>>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 parralel, and do the
block-job-complete to do 1 switch only.
I can adapt my patches serie to test.
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.
----- Mail original -----
De: "Wolfgang Bumiller" <w.bumil...@proxmox.com>
À: "aderumier" <aderum...@odiso.com>
Cc: "pve-devel" <firstname.lastname@example.org>
Envoyé: Mardi 18 Octobre 2016 11:07:35
Objet: 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
> >>Like this user can manage old and new vm after migration . and If something
> >>crash during the migration,this is more easier
> We could adapt vm_clone to be able to use remote local storage.
> then reuse vm_clone in 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.
pve-devel mailing list