From: Avi Kivity <avi@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: quintela@redhat.com, Anthony Liguori <anthony@codemonkey.ws>,
Umesh Deshpande <udeshpan@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [RFC] New thread for the VM migration
Date: Sun, 17 Jul 2011 11:39:10 +0300 [thread overview]
Message-ID: <4E229FAE.9000905@redhat.com> (raw)
In-Reply-To: <4E1FF360.8010609@redhat.com>
On 07/15/2011 10:59 AM, Paolo Bonzini wrote:
> On 07/14/2011 06:07 PM, Avi Kivity wrote:
>>
>> Maybe we can do this via a magic subsection whose contents are the
>> hotplug event.
>
> What about making the device list just another "thing" that has to be
> migrated live, together with block and ram?
Excellent idea.
Sticky points:
- if a new device includes RAM, the device update must precede the
migration of the new RAM section
- the reverse for unplug
- need better decoupling between host and guest state
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, Umesh Deshpande <udeshpan@redhat.com>,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC] New thread for the VM migration
Date: Sun, 17 Jul 2011 11:39:10 +0300 [thread overview]
Message-ID: <4E229FAE.9000905@redhat.com> (raw)
In-Reply-To: <4E1FF360.8010609@redhat.com>
On 07/15/2011 10:59 AM, Paolo Bonzini wrote:
> On 07/14/2011 06:07 PM, Avi Kivity wrote:
>>
>> Maybe we can do this via a magic subsection whose contents are the
>> hotplug event.
>
> What about making the device list just another "thing" that has to be
> migrated live, together with block and ram?
Excellent idea.
Sticky points:
- if a new device includes RAM, the device update must precede the
migration of the new RAM section
- the reverse for unplug
- need better decoupling between host and guest state
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-17 8:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <539565793.1312156.1310595395982.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com>
2011-07-13 23:34 ` [RFC] New thread for the VM migration Umesh Deshpande
2011-07-13 23:34 ` [Qemu-devel] " Umesh Deshpande
2011-07-14 7:14 ` Umesh Deshpande
2011-07-14 7:14 ` [Qemu-devel] " Umesh Deshpande
2011-07-14 8:36 ` Avi Kivity
2011-07-14 8:36 ` Avi Kivity
2011-07-14 9:09 ` Stefan Hajnoczi
2011-07-14 9:09 ` Stefan Hajnoczi
2011-07-14 12:30 ` Anthony Liguori
2011-07-14 12:32 ` Avi Kivity
2011-07-14 15:30 ` Juan Quintela
2011-07-14 15:30 ` [Qemu-devel] " Juan Quintela
2011-07-14 15:44 ` Avi Kivity
2011-07-14 15:44 ` [Qemu-devel] " Avi Kivity
2011-07-14 15:52 ` Juan Quintela
2011-07-14 15:52 ` [Qemu-devel] " Juan Quintela
2011-07-14 16:07 ` Avi Kivity
2011-07-14 16:07 ` [Qemu-devel] " Avi Kivity
2011-07-15 7:59 ` Paolo Bonzini
2011-07-15 7:59 ` Paolo Bonzini
2011-07-15 7:59 ` [Qemu-devel] " Paolo Bonzini
2011-07-15 21:09 ` Anthony Liguori
2011-07-15 21:09 ` Anthony Liguori
2011-07-17 8:39 ` Avi Kivity [this message]
2011-07-17 8:39 ` Avi Kivity
2011-07-18 7:08 ` Markus Armbruster
2011-07-18 7:08 ` Markus Armbruster
2011-07-14 16:49 ` Anthony Liguori
2011-07-14 16:59 ` Avi Kivity
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=4E229FAE.9000905@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=udeshpan@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 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.