From: Juan Quintela <quintela@redhat.com>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call agenda for Mar 16
Date: Tue, 16 Mar 2010 10:18:03 +0100 [thread overview]
Message-ID: <m3d3z439ro.fsf@trasno.mitica> (raw)
In-Reply-To: <20100316070155.GK3732@x200.localdomain> (Chris Wright's message of "Tue, 16 Mar 2010 00:01:55 -0700")
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).
- source side: current behaviour if migration fails is to stop the
vm. We have requests to make it continue (remember that this is
live migration). what to do? adding a paramenter like the block
layer:
migration_error=[stop|continue]
any better ideas.
- block migration: it added the set_params() callback, investigating
why. I think that it can be done with inside block_save_live(), but I
haven't investigated it fully yet.
Later, Juan.
> thanks,
> -chris
next prev parent reply other threads:[~2010-03-16 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 7:01 KVM call agenda for Mar 16 Chris Wright
2010-03-16 9:18 ` Juan Quintela [this message]
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
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=m3d3z439ro.fsf@trasno.mitica \
--to=quintela@redhat.com \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox