From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Treutner <thomas@scripty.at>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] A small patch to introduce stop conditions to the live migration.
Date: Thu, 15 Sep 2011 11:35:29 +0200 [thread overview]
Message-ID: <4E71C6E1.9060000@redhat.com> (raw)
In-Reply-To: <4E71B701.3070103@scripty.at>
On 09/15/2011 10:27 AM, Thomas Treutner wrote:
>
>> can always stop a guest to force convergence.
>
> What do you mean by stop exactly? Pausing the guest? Is it then
> automatically unpaused by qemu again at the destination host?
Whether the guest restarts on the destination depends on the -S
command-line option given in the destination.
libvirt in particular restarts the guest depending on the state *at the
beginning of migration*, so yes---pausing the guest will force
convergence and will get the guest running on the destination.
Paolo
prev parent reply other threads:[~2011-09-15 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 13:18 [Qemu-devel] [PATCH] A small patch to introduce stop conditions to the live migration Thomas Treutner
2011-09-14 15:22 ` Michael Roth
2011-09-14 15:36 ` Michael Roth
2011-09-14 15:45 ` Anthony Liguori
2011-09-15 8:27 ` Thomas Treutner
2011-09-15 9:35 ` Paolo Bonzini [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=4E71C6E1.9060000@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thomas@scripty.at \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).