From: "Daniel P. Berrange" <berrange@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call agenda for Mar 16
Date: Tue, 16 Mar 2010 10:09:39 +0000 [thread overview]
Message-ID: <20100316100939.GC23617@redhat.com> (raw)
In-Reply-To: <20100316092944.GB23617@redhat.com>
On Tue, Mar 16, 2010 at 09:29:44AM +0000, Daniel P. Berrange wrote:
> On Tue, Mar 16, 2010 at 10:18:03AM +0100, Juan Quintela wrote:
> > Chris Wright <chrisw@redhat.com> wrote:
> > > Please send in any agenda items you are interested in covering.
> >
> > Migration:
> > - flexible migration: I hope to sent an RFC patch on time for the
> > call. idea is to use subsections.
> >
> > - callbacks. block migration introduced several callbacks:
> > * cancel()
> > * get_status()
> > * release()
> > in spice we need now another to callbacks: on_start() and on_end().
> > * on_start(): tells spice that migration has started (it will then
> > manage certificates, passwords, ... itself)
> > * on_end(): it is called when migration ends. spice use it to
> > transparently connect to the new host and user don't have to "reconnect"
> >
> > - what to do on migration error:
> > - target side: libvirt folks want the program to print a message if
> > it fails. Current code spent 100% cpu time doing select on a closed
> > fd. (patches already on the list to make it wait without using
> > cpu).
>
> No, that is not correct. We want QEMU to exit when incoming migration
> fails. Printing to stderr is just something that will end up in the
> logs for admin to further diagnose the problem if required. There is
> nothing to be gained by leaving QEMU running, and everything to loose
> since the failed migration may have left it in a dangerous state from
> which you do not want to attempt incoming migration again.
Sorry, I forgot to include the original BZ report about this problem from
Fedora. In essence, we just truncated the original save state image and
then tried to restore from it to check handling in the event of corrupted
save image.
https://bugzilla.redhat.com/show_bug.cgi?id=518032
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
prev parent reply other threads:[~2010-03-16 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 7:01 [Qemu-devel] KVM call agenda for Mar 16 Chris Wright
2010-03-16 9:18 ` [Qemu-devel] " Juan Quintela
2010-03-16 9:29 ` Daniel P. Berrange
2010-03-16 9:43 ` Avi Kivity
2010-03-16 10:31 ` Daniel P. Berrange
2010-03-16 10:38 ` Avi Kivity
2010-03-16 10:45 ` Christoph Hellwig
2010-03-16 10:45 ` Daniel P. Berrange
2010-03-16 11:16 ` Avi Kivity
2010-03-16 15:05 ` Anthony Liguori
2010-03-16 15:23 ` Daniel P. Berrange
2010-03-16 15:46 ` Anthony Liguori
2010-03-16 10:09 ` Daniel P. Berrange [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=20100316100939.GC23617@redhat.com \
--to=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).