[pve-devel] qemu-server : qm copy

This add qm copy vmid vmiddest This duplicate vmid config, regenerate mac address, and copy disks for new vm. default destination storeid is the same than source storeid. default format (if file) is the same than source format. destinations storage and file format can be override with qm copy

[pve-devel] [PATCH 1/4] qm copy implementation

This add qm copy vmid vmiddest This duplicate vmid config, regenerate mac address, and copy disks for new vm. default destination storeid is the same than source storeid. default format (if file) is the same than source format. destinations storage and file format can be override with qm copy

[pve-devel] [PATCH] add $preparecopy argument to alloc_image

qemu-img convert need that target volume doesn't exist, so we only return the target volume name. exception is lvm and nexenta device, we need to create the volume and return the volumename Signed-off-by: Alexandre Derumier aderum...@odiso.com --- PVE/Storage.pm |4 ++--

Re: [pve-devel] pvestatd memory detection is too low

I agree too, an option could be fine . (/etc/default/pvestatd ?) - Mail original - De: Michael Rasmussen m...@datanom.net À: Stefan Priebe - Profihost AG s.pri...@profihost.ag, pve-devel@pve.proxmox.com Envoyé: Vendredi 26 Octobre 2012 13:33:21 Objet: Re: [pve-devel] pvestatd

Re: [pve-devel] memory leak in PVE/QMPClient.pm

please read my 2nd mail. This is sadly not enough. As perl things the circ. reference still exists when going out of scope. We habe to mark the self object in mux as weaken. Am 26.10.2012 15:24, schrieb Dietmar Maurer: To fix this we need a DESTROY function in QMPClient: sub DESTROY { my

Re: [pve-devel] pvestatd memory detection is too low

Instead, we should measure usage at startup (or first iteration), then allow to grow a few MBs? -Original Message- From: pve-devel-boun...@pve.proxmox.com [mailto:pve-devel- boun...@pve.proxmox.com] On Behalf Of Stefan Priebe - Profihost AG Sent: Freitag, 26. Oktober 2012 13:23 To:

Re: [pve-devel] [PATCH 1/4] qm copy implementation

Subject: [pve-devel] [PATCH 1/4] qm copy implementation Is that copy/past from somewhere? ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] pve-storage : add $preparecopy argument to alloc_image

qemu-img convert need that target volume doesn't exist, so we only return the target volume name. The suggestion was to modify qemu-img instead. ___ pve-devel mailing list pve-devel@pve.proxmox.com

Re: [pve-devel] pvestatd memory detection is too low

Another idea could be to get memory consumption after two circles and restart if memory raises by 10%. But at all no Daemon should restart automatically leaks must be found and removed. Exactly! ___ pve-devel mailing list

Re: [pve-devel] qemu-server : qm copy

Current implement don't copy snapshots, and copy disks from you are here state But this only works if the VM is stopped? I am asking this, because new backup can store running VMs, so a backup/restore pipe can do that job. ___ pve-devel mailing list

Re: [pve-devel] qemu-server : qm copy

But this only works if the VM is stopped? I am asking this, because new backup can store running VMs, so a backup/restore pipe can do that job. Yes, I don't have work yet on snapshot.(not difficult to implement, qemu-img support it) - Mail original - De: Dietmar Maurer

Re: [pve-devel] [PATCH 1/4] qm copy implementation

Is that copy/past from somewhere? I take vm_create as template (as disk create is similar) - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre Derumier aderum...@odiso.com, pve-devel@pve.proxmox.com Envoyé: Vendredi 26 Octobre 2012 15:44:44 Objet: RE: [pve-devel]