From: Anthony Liguori <aliguori@us.ibm.com>
To: Glauber Costa <glommer@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH alternative] fix migration to obey -S
Date: Mon, 27 Jul 2009 18:13:14 -0500 [thread overview]
Message-ID: <4A6E348A.4090904@us.ibm.com> (raw)
In-Reply-To: <20090727231541.GP4776@poweredge.glommer>
Glauber Costa wrote:
> On Mon, Jul 27, 2009 at 04:36:53PM -0500, Anthony Liguori wrote:
>
>> Glauber Costa wrote:
>>
>>> 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.
>>>
>>>
>> 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.
>>
> 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 parent reply other threads:[~2009-07-27 23:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 20:20 [Qemu-devel] [PATCH] fix broken migration Glauber Costa
2009-07-25 1:37 ` [Qemu-devel] " Paolo Bonzini
2009-07-27 18:02 ` Glauber Costa
2009-07-27 19:31 ` Paolo Bonzini
2009-07-27 20:18 ` Glauber Costa
2009-07-27 21:08 ` [Qemu-devel] [PATCH] fix migration to not require -S Paolo Bonzini
2009-07-27 21:17 ` [Qemu-devel] [PATCH alternative] fix migration to obey -S Paolo Bonzini
2009-07-27 21:29 ` [Qemu-devel] " Glauber Costa
2009-07-27 21:36 ` Anthony Liguori
2009-07-27 23:15 ` Glauber Costa
2009-07-27 23:13 ` Anthony Liguori [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A6E348A.4090904@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=glommer@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.