Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

m> Cc: "Wolfgang Bumiller" <w.bumil...@proxmox.com>, "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mercredi 19 Octobre 2016 10:18:41 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration > On October 19, 2016 at 9:26 AM

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

: "aderumier" <aderum...@odiso.com> À: "dietmar" <diet...@proxmox.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mercredi 19 Octobre 2016 10:33:21 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration >>Somethi

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

lt;w.bumil...@proxmox.com>, "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mercredi 19 Octobre 2016 10:18:41 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration > On October 19, 2016 at 9:26 AM Alexandre DERUMIER <aderum...@odiso.com> > w

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

> On October 19, 2016 at 9:26 AM Alexandre DERUMIER wrote: > > > >>What about the suggestion from Wolfgang: "make drive-mirror write to both > >>disks" > >>(local and remote) > >> > >>I guess that would solve the whole problem? > > Do you mean, keep the drive-mirror

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

@proxmox.com> À: "aderumier" <aderum...@odiso.com>, "dietmar" <diet...@proxmox.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mercredi 19 Octobre 2016 09:41:50 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration &g

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

ode except it only has one disk, so I doubt that's possible/implemented). > - Mail original - > De: "dietmar" <diet...@proxmox.com> > À: "Wolfgang Bumiller" <w.bumil...@proxmox.com>, "aderumier" > <aderum...@odiso.com>, &quo

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

...@odiso.com>, "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 18 Octobre 2016 17:40:35 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration > The only think: > > I still don't known how to manage the case of target node crash after

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

> 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. What about the suggestion from Wolfgang: "make drive-mirror write to both disks" (local and remote) I guess that would solve the whole problem?

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

- De: "Wolfgang Bumiller" <w.bumil...@proxmox.com> À: "aderumier" <aderum...@odiso.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 18 Octobre 2016 11:07:35 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migra

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

l disk. (no orphans disk in case of node failure during a migration for example) - Mail original - De: "dietmar" <diet...@proxmox.com> À: "aderumier" <aderum...@odiso.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 18 Octobre 201

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 > >>config. > >>Like this user can manage old and new vm after migration . and If something > >>crash during the migration,this is more easier > > We

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

> > The only drawback is that we can't mix local && shared storage in this case. > > (but I think that if user have shared storage, he don't have need of local > > storage migration) > > >>Not sure if this is a good restriction (Maybe this is a major use case). > > Note that you can have

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

> Another possibility : create a new vmid on target host, with his own config. > Like this user can manage old and new vm after migration . and If something > crash during the migration,this is more easier. > > The only drawback is that we can't mix local && shared storage in this case. > (but

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

hen reuse vm_clone in vm migration. - Mail original - De: "aderumier" <aderum...@odiso.com> À: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 18 Octobre 2016 01:05:16 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration >&g

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

need of local storage migration) - Mail original - De: "aderumier" <aderum...@odiso.com> À: "Wolfgang Bumiller" <w.bumil...@proxmox.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Lundi 17 Octobre 2016 15:52:14 Objet: Re: [pve-devel

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

e: "Wolfgang Bumiller" <w.bumil...@proxmox.com> À: "aderumier" <aderum...@odiso.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Lundi 17 Octobre 2016 15:41:49 Objet: Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

On Mon, Oct 17, 2016 at 03:33:38PM +0200, Alexandre DERUMIER wrote: > >>considering some of the code looks like it's prepared for multiple > >>disks, I wonder if the remote side should send a mapping containing the > >>old + new names? > > yes, I think it can prepare output for multiple disks,

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

ion, to known where the local disk is located exactly. I'm not sure... - Mail original - De: "Wolfgang Bumiller" <w.bumil...@proxmox.com> À: "aderumier" <aderum...@odiso.com> Cc: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Lundi 17

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

On Tue, Oct 11, 2016 at 04:45:19PM +0200, Alexandre Derumier wrote: > This allow to migrate a local storage (only 1 for now) to a remote node > storage. > > When the target node start, a new volume is created and exposed through qemu > embedded nbd server. > > qemu drive-mirror is done on

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

ready done on target storage). That's why I force stop of source vm and migrate config file on target. - Mail original - De: "Thomas Lamprecht" <t.lampre...@proxmox.com> À: "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mercredi 12 Octobre 2016 09:4

Re: [pve-devel] [PATCH 1/3] add live storage migration with vm migration

comments inline On 10/11/2016 04:45 PM, Alexandre Derumier wrote: This allow to migrate a local storage (only 1 for now) to a remote node storage. When the target node start, a new volume is created and exposed through qemu embedded nbd server. qemu drive-mirror is done on source vm with nbd

[pve-devel] [PATCH 1/3] add live storage migration with vm migration

This allow to migrate a local storage (only 1 for now) to a remote node storage. When the target node start, a new volume is created and exposed through qemu embedded nbd server. qemu drive-mirror is done on source vm with nbd server as target. when drive-mirror is done, the source vm is