> hostX:$vmid/vm-$vmid-disk-N.{raw,qcow2} -> hostY:$vmid/vm-$vmid-disk- > N.{raw,qcow2} >>Yes, I guess that is easy to implement (for local storage migration).
I'll already working in my paches (qemu-img or drive-mirror) >>Would it be possible to do all work using 'qmp' commands. We can simply start >>the VM >>if the VM is offline (paused state). I currently do that with the new backup >>code. >> >>I guess that would make the whole thing much simpler? Not sure about that, About my templates patches, I can see one better thing with qemu-img, we can copy multiple time at once. with drive-mirror, we can only do 1 drive-mirror job at once. ----- Mail original ----- De: "Dietmar Maurer" <diet...@proxmox.com> À: "Michael Rasmussen" <m...@datanom.net>, pve-devel@pve.proxmox.com Envoyé: Dimanche 20 Janvier 2013 11:15:56 Objet: Re: [pve-devel] vm migration + storage migration with ndb workflow notes > > I just think this is enough for remote migration. > > > > For local VMs we can have storage migration between any accessible > storage. > > > I second this. > > Just a thought: Would it not be of interest for the users to be able to > change > storage format? > > eg. > hostX:$vmid/vm-$vmid-disk-N.{raw,qcow2} -> hostY:$vmid/vm-$vmid-disk- > N.{raw,qcow2} Yes, I guess that is easy to implement (for local storage migration). > Both drive-mirror and qemu-img convert can do this on the fly and some > format change needs to be supported anyway if storage change from file > system to block device. Would it be possible to do all work using 'qmp' commands. We can simply start the VM if the VM is offline (paused state). I currently do that with the new backup code. I guess that would make the whole thing much simpler? _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel