Re: [pve-devel] pve-kernel

> Backported targetcli-fb (binary and source) included dependencies can > get downloaded here: > http://ftp.datanom.net/pve/targetcli-fb-backports.tgz What did you change exactly? The changelogs just mentions: * Rebuild for jessie-backports. Something else changed? And did you already run some

Re: [pve-devel] pve-kernel

On Tue, 18 Oct 2016 17:34:15 +0200 (CEST) Dietmar Maurer wrote: > > If I backport targetcli from stretch would you accept the package? > > yes > > > BTW. Seems Redhat/Fedora/Ubuntu/Debian have forked the original > > targetcli to targetcli-fb so it seems advisable to

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

> The only think: > > I still don't known how to manage the case of target node crash after the disk > are migrate, but vm still on source node. What about the suggestion from Wolfgang: "make drive-mirror write to both disks" (local and remote) I guess that would solve the whole problem?

Re: [pve-devel] pve-kernel

> If I backport targetcli from stretch would you accept the package? yes > BTW. Seems Redhat/Fedora/Ubuntu/Debian have forked the original > targetcli to targetcli-fb so it seems advisable to follow this path. Yes. ___ pve-devel mailing list

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

>>That sounds worse ;-) >>The only real solution is to make drive-mirror write to both disks in a >>raid-1 fashion once the initial sync is completed in order to be able to >>detach the destination in an error case without losing data. yes, I think it's possible to use multiple drive-mirror in

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

>>I don't really understand that. I thought we will only migrate local disks. >>IMHO >>it makes no >>sense to migrate a shared disk to a local storage? It was in case of my 2nd proposal of new vmid for target. The advantage was that each vm.conf have their own local disk. (no orphans disk in

[pve-devel] [PATCH container] vmstatus: fix memory usage value including cache sizes

The cgroup value memory.usage_in_bytes includes the memory used by file buffers and other caches, resolve this by getting the cache value from the memory.stat file and substract it from memory.usage_in_bytes when calculating the current memory usage of the CT. This results in the same value as a

Re: [pve-devel] pve-kernel

On Tue, 18 Oct 2016 14:25:10 +0200 (CEST) Dietmar Maurer wrote: > > Sure. But what we need is a working, fast, iscsi target. > So we need the lio userspace tool, which are hopefully available > in next Debian... > If I backport targetcli from stretch would you accept the

Re: [pve-devel] pve-kernel

On Tue, 18 Oct 2016 13:02:39 +0200 (CEST) Dietmar Maurer wrote: > > Therefore I suggest to tag the pve-kernel-4.x so that it conflicts with > > iscsitarget-dkms. > > What for? The user will notice that it does not compile anyways? I guess > there are many dkms modules

Re: [pve-devel] pve-kernel

> Therefore I suggest to tag the pve-kernel-4.x so that it conflicts with > iscsitarget-dkms. What for? The user will notice that it does not compile anyways? I guess there are many dkms modules that does not compile with our kernel. ___ pve-devel

[pve-devel] applied: [PATCH manager v2 0/2] Remove global variables from Utils.js

___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] pve-kernel

Hi all, See my reply here: https://forum.proxmox.com/threads/low-overhead-low-level-method-of-sharing-filesystems.29691/#post-149715 The removal request for Debian can be found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834523 Therefore I suggest to tag the pve-kernel-4.x so that

[pve-devel] [PATCH manager v2 2/2] Move globally defined regexpes into PVE.Utils

Those globally defined regexpes were only used in Toolkit.js --- www/manager6/Toolkit.js | 20 +++--- www/manager6/Utils.js | 70 - 2 files changed, 44 insertions(+), 46 deletions(-) diff --git a/www/manager6/Toolkit.js

[pve-devel] [PATCH manager v2 0/2] Remove global variables from Utils.js

Changes since V1: * rebase * drop trailing coma fox in OsDefaults, as it was fixed in between Emmanuel Kasper (2): Turn PVE.Utils into a singleton Move globally defined regexpes into PVE.Utils www/manager6/Toolkit.js | 20 ++-- www/manager6/Utils.js | 82

[pve-devel] [PATCH manager v2 1/2] Turn PVE.Utils into a singleton

This will allow us to add contructed values ( regexp a = stringA + stringB ) into the constructor. Access to the PVE.Utils properties and methods stays the same. --- www/manager6/Utils.js | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/www/manager6/Utils.js

Re: [pve-devel] [PATCH RESEND qemu-server] Fix #1174: remove pve-qm-drive

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH openvswitch 1/4] New Version OVS 2.6.0

--- Makefile | 4 ++-- changelog.Debian | 6 ++ 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 7578b27..1e3acb3 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ -RELEASE=4.2 +RELEASE=4.3 # also add entry in changelog.Debian

[pve-devel] [PATCH openvswitch 2/4] Make quilt patches working for OVS 2.6

--- pvepatches/fix-init-script-patch | 21 - pvepatches/install-systemd-services.patch | 62 +-- pvepatches/remove-unneeded-from-control.patch | 17 3 files changed, 39 insertions(+), 61 deletions(-) diff --git

[pve-devel] [PATCH openvswitch 3/4] Change download source to githup.

2014 OVS say githup is the new official git repository. http://openvswitch.org/pipermail/announce/2014-April/63.html --- Makefile | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/Makefile b/Makefile index 1e3acb3..87c882a 100644 --- a/Makefile +++ b/Makefile @@

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

On Tue, Oct 18, 2016 at 01:50:37AM +0200, Alexandre DERUMIER wrote: > >>Another possibility : create a new vmid on target host, with his own > >>config. > >>Like this user can manage old and new vm after migration . and If something > >>crash during the migration,this is more easier > > We

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

> > The only drawback is that we can't mix local && shared storage in this case. > > (but I think that if user have shared storage, he don't have need of local > > storage migration) > > >>Not sure if this is a good restriction (Maybe this is a major use case). > > Note that you can have

Re: [pve-devel] [PATCH docs] Update the qm command line example to use the new volume format

> - qm create 300 -ide0 4 -net0 e1000 -cdrom proxmox-mailgateway_2.1.iso > + qm create 300 -ide0 local-lvm:4 -ide2 > local:iso/proxmox-mailgateway_4.0-7.iso,media=cdrom Why don't we keep the cdrom parameter? qm create 300 -ide0 local-lvm:4 -cdrom local:iso/proxmox-mailgateway_4.0-7.iso > + >

[pve-devel] Applied: [PATCH v2 common] SectionConfig: always write out explicitly set booleans

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH kernel] Fix #927: add IPoIB performance regression fix

On Fri, Oct 14, 2016 at 08:05:56AM +0200, Michael Rasmussen wrote: > On Thu, 13 Oct 2016 16:49:30 +0200 > Wolfgang Bumiller wrote: > > > Fixes kernel bug #111921 > > --- > > ...ck-the-IB-LL-address-into-the-hard-header.patch | 365 > > + > > Makefile

[pve-devel] [PATCH RESEND qemu-server] Fix #1174: remove pve-qm-drive

Let 'cdrom' use the pve-qm-ide format, as it's supposed to be an alias to ide2. We're not using the 'alias' schema property since the qemu configs still use a custom parser (due to the pending-changes system and the filename-to-volume-id conversion for legacy support) which does not deal with

Re: [pve-devel] [PATCH docs] Add subchapter documenting the startup/shutdown options

On 10/18/2016 09:29 AM, Dietmar Maurer wrote: > applied. But we have the same feature for containers? Yes. A patch will follow for containers. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [RFC common] add 'pve-vmid-optional' format and standard option

On 10/18/2016 08:56 AM, Fabian Grünbichler wrote: On Mon, Oct 17, 2016 at 05:44:34PM +0200, Thomas Lamprecht wrote: This will be used in cases where the VMID may not be important. For example some users do not care which VMID a CT/VM gets, they just want a CT/VM. Signed-off-by: Thomas

Re: [pve-devel] [PATCH qemu-server] Fix typo

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH docs] Add subchapter documenting the startup/shutdown options

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] Fix Bug #889 and allow automatic VMID selection on create

On 10/18/2016 08:49 AM, Fabian Grünbichler wrote: On Mon, Oct 17, 2016 at 05:44:31PM +0200, Thomas Lamprecht wrote: The get /cluster/nextid API call is not secured against race conditions and parallel accesses in general. Users of the API which created multiple CT in parallel or at least very

Re: [pve-devel] [RFC common] add 'pve-vmid-optional' format and standard option

On Mon, Oct 17, 2016 at 05:44:34PM +0200, Thomas Lamprecht wrote: > This will be used in cases where the VMID may not be important. For > example some users do not care which VMID a CT/VM gets, they just > want a CT/VM. > > Signed-off-by: Thomas Lamprecht > --- >

Re: [pve-devel] Fix Bug #889 and allow automatic VMID selection on create

On Mon, Oct 17, 2016 at 05:44:31PM +0200, Thomas Lamprecht wrote: > The get /cluster/nextid API call is not secured against race conditions and > parallel accesses in general. > Users of the API which created multiple CT in parallel or at least very fast > after each other run into problems here: