[libvirt] [RFC PATCH 00/12] qemu: add support to hot-plug/unplug cpu device
Daniel P. Berrange
berrange at redhat.com
Thu Jan 22 10:04:47 UTC 2015
On Thu, Jan 22, 2015 at 04:57:39PM +0800, Zhu Guihua wrote:
> On Wed, 2015-01-21 at 09:57 +0000, Daniel P. Berrange wrote:
> > On Wed, Jan 21, 2015 at 04:00:52PM +0800, Zhu Guihua wrote:
> > > If you apply the folowing patchset
> > > [PATCH v3 0/7] cpu: add device_add foo-x86_64-cpu support
> > > https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg01552.html,
> > > and [PATCH v2 00/11] cpu: add i386 cpu hot remove support
> > > https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg01557.html,
> > > qemu can support hotplug and hot-unplug cpu device.
> > >
> > > So this patch series will make libvirt support hotplug and hot-unplug cpu
> > > device for qemu driver, and now only supports one cpu driver which is
> > > 'qemu64-x86_64-cpu'.
> > Also I'm wondering how this interacts with CPU topology. eg lets say
> > you configure a 16 vCPU guest, and set topology to 2 sockets, 4 cores,
> > 2 threads. Does this hotplug allow you to plug/unplug individual
> > threads - ie each invididual vCPU, or does it only allow plug/unplug
> > of sockets - ie 8 vCPUs at a time in this topology.
> qemu has not interacted with CPU topology so for.
> So now we focus on this feature's realization in a simple way.
What do you mean by that ? eg which impl I describe above will it support ?
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
More information about the libvir-list