Re: [pve-devel] some finding avout minimum static memory when pc-dimm exists

2015-01-23 Thread Dietmar Maurer
I am also thinking about changing the 'hotplug' config like this: hotplug: [mem|cpu|net|disk][,mem|cpu|net|disk]* so that we can selectively enable them. On January 23, 2015 at 6:59 PM Dietmar Maurer diet...@proxmox.com wrote: Like this we only need 1 memory option (min:512), which seem

Re: [pve-devel] some finding avout minimum static memory when pc-dimm exists

2015-01-23 Thread Dietmar Maurer
But maybe could be do something like: without dimm hotplug [CONF] memory: 1024 kvm -m 1024 with dimm hotplug -- [CONF] memory: 1024 maxmemory: 8192 (this enable dimm hotplug) kvm -m size=512,slots=255,maxmemory=8192 -pcdimm 512M

Re: [pve-devel] some finding avout minimum static memory when pc-dimm exists

2015-01-23 Thread Dietmar Maurer
Like this we only need 1 memory option (min:512), which seem easier for user. What do you think about it ? Also, from my point of view we can require a limit of 1GB mem. I guess this would be safer to boot. ___ pve-devel mailing list

Re: [pve-devel] some finding avout minimum static memory when pc-dimm exists

2015-01-23 Thread Dietmar Maurer
On January 23, 2015 at 6:59 PM Dietmar Maurer diet...@proxmox.com wrote: Like this we only need 1 memory option (min:512), which seem easier for user. What do you think about it ? Also, from my point of view we can require a limit of 1GB mem. I guess this would be safer to

Re: [pve-devel] qemu 2.1.3 release

2015-01-23 Thread Alexandre DERUMIER
Please can you verify if that patch is already applied in 2.2? yes ! - Mail original - De: dietmar diet...@proxmox.com À: aderumier aderum...@odiso.com, pve-devel pve-devel@pve.proxmox.com Envoyé: Vendredi 23 Janvier 2015 15:52:32 Objet: Re: [pve-devel] qemu 2.1.3 release oh sorry, we

[pve-devel] some finding avout minimum static memory when pc-dimm exists

2015-01-23 Thread Alexandre DERUMIER
Hi, I have done some tests, and it's seem that the minimum memory when pc-dimm exists, is 512MB (I have read some discussion mailing about pci hole, but I don't understand all the things ;). On a linux machine booting fine with -m 128 , it don't work with -m 128 -pcdimm 1024 ... for example.

Re: [pve-devel] qemu 2.1.3 release

2015-01-23 Thread Alexandre DERUMIER
oh sorry, we are already at 2.2 version ;) - Mail original - De: aderumier aderum...@odiso.com À: pve-devel pve-devel@pve.proxmox.com Envoyé: Vendredi 23 Janvier 2015 14:32:38 Objet: [pve-devel] qemu 2.1.3 release 1 interesting fix: migration/block: fix pending() return value

Re: [pve-devel] ZfsDirPlugin

2015-01-23 Thread Dietmar Maurer
OK, I applied that after fixing several small bugs. We need to test now. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] ZfsDirPlugin

2015-01-23 Thread Wolfgang Link
this is the refactoring of ZfsPlugin and implement ZFSDirPlugin In-Reply-To: ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH 9/9] zfs: move and refactor code

2015-01-23 Thread Wolfgang Link
copy and modify create_base and refactor clone_image Signed-off-by: Wolfgang Link w.l...@proxmox.com --- PVE/Storage/ZFSDirPlugin.pm | 43 +++ PVE/Storage/ZFSPlugin.pm| 13 + 2 files changed, 44 insertions(+), 12 deletions(-) diff

[pve-devel] [PATCH 3/9] zfs: copy free_image

2015-01-23 Thread Wolfgang Link
modify it for ZFSDirPlugin. Signed-off-by: Wolfgang Link w.l...@proxmox.com --- PVE/Storage/ZFSDirPlugin.pm | 11 +++ 1 file changed, 11 insertions(+) diff --git a/PVE/Storage/ZFSDirPlugin.pm b/PVE/Storage/ZFSDirPlugin.pm index da53525..e3c1a9d 100644 --- a/PVE/Storage/ZFSDirPlugin.pm

[pve-devel] [PATCH 7/9] zfs: move code

2015-01-23 Thread Wolfgang Link
move activate_volume deactivate_volume from ZFSPlugin to ZFSDirPlugin Signed-off-by: Wolfgang Link w.l...@proxmox.com --- PVE/Storage/ZFSDirPlugin.pm |9 + PVE/Storage/ZFSPlugin.pm| 10 -- 2 files changed, 9 insertions(+), 10 deletions(-) diff --git

[pve-devel] [PATCH 5/9] zfs: ZFSDirPlugin add methode path

2015-01-23 Thread Wolfgang Link
Signed-off-by: Wolfgang Link w.l...@proxmox.com --- PVE/Storage/ZFSDirPlugin.pm | 16 1 file changed, 16 insertions(+) diff --git a/PVE/Storage/ZFSDirPlugin.pm b/PVE/Storage/ZFSDirPlugin.pm index fb7a1a2..260e328 100644 --- a/PVE/Storage/ZFSDirPlugin.pm +++

[pve-devel] [PATCH 6/9] zfs: fix insert return at alloc_immage

2015-01-23 Thread Wolfgang Link
Signed-off-by: Wolfgang Link w.l...@proxmox.com --- PVE/Storage/ZFSDirPlugin.pm |1 + 1 file changed, 1 insertion(+) diff --git a/PVE/Storage/ZFSDirPlugin.pm b/PVE/Storage/ZFSDirPlugin.pm index 260e328..1782c04 100644 --- a/PVE/Storage/ZFSDirPlugin.pm +++ b/PVE/Storage/ZFSDirPlugin.pm @@

Re: [pve-devel] qemu-server : cpu hotplug rework

2015-01-23 Thread Alexandre DERUMIER
I just applied the vcpu patches. But I am a bit clueless how to present that on the GUI. Yes, same for me. (BTW, I'm testing cpu hot-unplug patchs, seem to be in good shape, works fine here. (maybe some minor bugs). So maybe it'll be include in qemu 2.3.) - Mail original - De:

[pve-devel] qemu 2.1.3 release

2015-01-23 Thread Alexandre DERUMIER
1 interesting fix: migration/block: fix pending() return value http://lists.gnu.org/archive/html/qemu-devel/2015-01/msg01274.html Because of wrong return value of .save_live_pending() in migration/block.c, migration finishes before the whole disk is transferred. Such situation occurs when the

Re: [pve-devel] qemu 2.1.3 release

2015-01-23 Thread Dietmar Maurer
oh sorry, we are already at 2.2 version ;) Please can you verify if that patch is already applied in 2.2? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] qemu 2.1.3 release

2015-01-23 Thread Stefan Priebe - Profihost AG
This is the fix i already mentioned at Jan 2nd 2015 on this ml. Stefan Excuse my typo sent from my mobile phone. Am 23.01.2015 um 15:52 schrieb Dietmar Maurer diet...@proxmox.com: oh sorry, we are already at 2.2 version ;) Please can you verify if that patch is already applied in 2.2?