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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
