* Migrating Vm's from one machine to another...and back
@ 2008-08-11 15:19 Jean-Pierre Dion
2008-08-11 17:01 ` Chris Lalancette
0 siblings, 1 reply; 3+ messages in thread
From: Jean-Pierre Dion @ 2008-08-11 15:19 UTC (permalink / raw)
To: kvm; +Cc: Laurent Vivier
Hi,
I made some VM migrations between several machines
(Intel-Intel and Intel-AMD) and when one VM has been
migrated onto a second machine, I cannot put it
back on the first one. I talked with Laurent and it
seems that there is no way (or no obvious one)
to do that.
This could be useful when doing some tasks (load
balancing...).
Is it an item that is interesting enough to be done ?
And does anyone have some idea on how to do that ?
Thanks for any idea/help.
jean-pierre
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Migrating Vm's from one machine to another...and back
2008-08-11 15:19 Migrating Vm's from one machine to another...and back Jean-Pierre Dion
@ 2008-08-11 17:01 ` Chris Lalancette
0 siblings, 0 replies; 3+ messages in thread
From: Chris Lalancette @ 2008-08-11 17:01 UTC (permalink / raw)
To: Jean-Pierre Dion; +Cc: kvm, Laurent Vivier
Jean-Pierre Dion wrote:
> Hi,
>
> I made some VM migrations between several machines
> (Intel-Intel and Intel-AMD) and when one VM has been
> migrated onto a second machine, I cannot put it
> back on the first one. I talked with Laurent and it
> seems that there is no way (or no obvious one)
> to do that.
>
> This could be useful when doing some tasks (load
> balancing...).
>
> Is it an item that is interesting enough to be done ?
> And does anyone have some idea on how to do that ?
Hm, this seems to work for me, in combination with my recently posted "Implement
tcp nowait option" patch. Basically you start the guest on machine A like
normal. Then you start the "container" on machine B with the -incoming flags.
Now you migrate the guest over to machine B (I assume you've gotten this far).
Now, you kill the container on machine A (since the running guest is on B now),
and restart it with -incoming. Now you migrate back from B to A, and it all
works out.
You can actually probably get rid of one of these steps by starting the machine
on machine A in the first place with -S -incoming tcp://0:4444,nowait, and then
running "cont" in the monitor. In this case, the machine is already running,
and *also* listening for incoming migrate requests. Now you do exactly the same
on machine B, and you should be able to migrate back and forth between them at will.
Chris Lalancette
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Migrating Vm's from one machine to another...and back
@ 2008-08-19 20:21 Jean-Pierre Dion
0 siblings, 0 replies; 3+ messages in thread
From: Jean-Pierre Dion @ 2008-08-19 20:21 UTC (permalink / raw)
To: clalance; +Cc: kvm
Hi Chris,
thank you for your advice.
I tried but did not succeed yet.
I experienced some issues with tcp mode.
I will retry when I am back from vacation next week.
I will tell you.
jean-pierre
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-08-19 20:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-11 15:19 Migrating Vm's from one machine to another...and back Jean-Pierre Dion
2008-08-11 17:01 ` Chris Lalancette
-- strict thread matches above, loose matches on Subject: below --
2008-08-19 20:21 Jean-Pierre Dion
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox