From: Avi Kivity <avi@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: KVM devel mailing list <kvm@vger.kernel.org>,
Dor Laor <dlaor@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] KVM call minutes April 3
Date: Thu, 05 Apr 2012 19:16:48 +0300 [thread overview]
Message-ID: <4F7DC570.6070003@redhat.com> (raw)
In-Reply-To: <20120404143944.GA2905@illuin>
On 04/04/2012 05:39 PM, Michael Roth wrote:
> > Will command line take in account hot-plugged devices?
>
> No, that's a good point. We'd probably need to generate the options
> required to ensure the devices are created on the target, and we'd only
> be able to do that just before sending the device state. That means we
> need a way to create machines after we've completed tasks like memory
> migration, which probably has similar requirements to just being able to
> instantiate a machine from a serialized QOM composition tree.
>
Or we forward the hotplug events over the migration protocol. This is
needed for devices that include memory (like ivshmem.c)
<page>
<page>
<page>
<hotplug event>
<page>
<page for the new device>
<page>
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-04-05 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 14:43 [Qemu-devel] KVM call minutes April 3 Markus Armbruster
2012-04-03 20:43 ` Dor Laor
2012-04-04 1:18 ` Michael Roth
2012-04-04 7:40 ` Paolo Bonzini
2012-04-04 10:37 ` Michael Roth
2012-04-04 10:53 ` Dor Laor
2012-04-04 11:52 ` Anthony Liguori
2012-04-04 12:01 ` Dor Laor
2012-04-04 12:14 ` Michael Roth
2012-04-04 13:21 ` Igor Mammedov
2012-04-04 14:39 ` Michael Roth
2012-04-05 16:16 ` Avi Kivity [this message]
2012-04-04 11:48 ` Anthony Liguori
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=4F7DC570.6070003@redhat.com \
--to=avi@redhat.com \
--cc=armbru@redhat.com \
--cc=dlaor@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mdroth@linux.vnet.ibm.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 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).