Re: [pve-devel] qemu-server : qm copy implementation V2
- always alloc image before copy (need qemu-img patch to skip bdrv create) - add -snapname option. (only qcow2 for now, as qemu-img convert -s snapname, work only with qcow2) - check if vm is running or not. (qemu-img convert with qcow2 snapshot work online) - cdrom : replace by none if cdrom exist in source config - replace vm name by vm name-copy - add target storeid permission check - display qemu-img percentage progression Need to be implemented : export/import from snapshot for other storage (wait for new backup framework) I will wait until I finish the backup framework. We need to factor out common code, or integrate 'copy' into 'create' Note: 'copy', 'create', 'restore' should all use the same code base. A first start would be to allow 'restore' to specify the target storage for each device - as you do for copy. - Dietmar ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] qemu-server : qm copy implementation V2
Need to be implemented : export/import from snapshot for other storage (wait for new backup framework) Note: By backup framework does not consider internal snapshots. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] qemu-server : qm copy implementation V2
Note: By backup framework does not consider internal snapshots. Ok no problem, so it'll work with lvm :) for raw and qcow2, you'll use external snapshots ? I see that block-commit qmp will be available for qemu 1.3. (to merge snapshot to parent file) http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg05210.html - Mail original - De: Dietmar Maurer diet...@proxmox.com À: Alexandre Derumier aderum...@odiso.com, pve-devel@pve.proxmox.com Envoyé: Mardi 30 Octobre 2012 07:57:29 Objet: RE: [pve-devel] qemu-server : qm copy implementation V2 Need to be implemented : export/import from snapshot for other storage (wait for new backup framework) Note: By backup framework does not consider internal snapshots. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] qemu-server : qm copy implementation V2
Note: By backup framework does not consider internal snapshots. Ok no problem, so it'll work with lvm :) for raw and qcow2, you'll use external snapshots ? No, I will not use any of that (no lvm, no internal snapshot, no external snapshots). ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
Re: [pve-devel] qemu-server : qm copy
You can't use qmu-img while the VM is running. Oh, didn't know that. (I thinked that's is worked with snapshot) But yes, we can re-use your backup/restore, it's better to reuse code and not doing twice the job). Does it work with all storage ? (rbd doesn't seem to be able to import from stdin) I am working on a better qemu based backup, which works on any storage (something like live-backup). First tests are promising, but I need one more week until I have something to show. ___ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
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 pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
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 diet...@proxmox.com À: Alexandre Derumier aderum...@odiso.com, pve-devel@pve.proxmox.com Envoyé: Vendredi 26 Octobre 2012 16:00:02 Objet: 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 pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
