|
From: | Anthony Liguori |
Subject: | [Qemu-devel] Re: [PATCH alternative] fix migration to obey -S |
Date: | Mon, 27 Jul 2009 18:13:14 -0500 |
User-agent: | Thunderbird 2.0.0.21 (X11/20090320) |
Glauber Costa wrote:
On Mon, Jul 27, 2009 at 04:36:53PM -0500, Anthony Liguori wrote:Glauber Costa wrote:Whether a guest is running is not part of it's state-IOW, it's not visible to the guest whether it's running or not.Hummm,, those are a little bit weird. I'd expect it to be a characteristic of the source machine, no the destination. IOW, if the machine was running prior to migration, it should be running after it, and if it was stopped prior to migration, it should be stopped after it.Can't we then register a savevm function for that?
No, that's the point. Since it's not guest visible, it should not be saved as part of savevm.
It's up to the management tools to keep track of whether a VM is stopped or not. When creating the destination node, the user specify whether they want the VM to be stopped.
So qemu -incoming ... -S Should translate to: do not automatically run the VM after migration. qemu -incoming ...Will always run the VM after migration regardless of whether the VM was migrated while stopped.
-- Regards, Anthony Liguori
[Prev in Thread] | Current Thread | [Next in Thread] |