[pve-devel] qemu2.7: cpu hotplug && hot-unplug v1
w.bumiller at proxmox.com
Wed Sep 7 09:02:13 CEST 2016
I pushed my current qemu-2.7 WIP to github.
It seems to work, still needs more testing & some cleanup (need to
squash all those small fixes for the older patches together).
I dropped the patch which adds support for a secondary server for
glusterfs as qemu can do this now - with a different syntax.
Although I haven't yet seen where we've been using this, or if at all?
I keep the github branches mostly in sync with our patch directories:
* The pve-2.7 branch contains the pve related patches based on the release
we build on (in this case the tag v2.7.0-rc4), these are the patches in
pve-qemu-kvm's debian/patches/pve/ directory.
* The extra-2.7 branch is always based on the pve branch and contains
patches from the qemu-stable/devel list (stable fixes, cve fixes etc.)
On Tue, Sep 06, 2016 at 12:41:52PM +0200, Alexandre Derumier wrote:
> This patch series implement new qemu 2.7 cpu hotplug framework, with device_add|device_del
> hot-unplug is working now !
> config example:
> cpu: kvm64
> generate cmdline
> -cpu kvm64,+lahf_lm,+sep,+kvm_pv_unhalt,+kvm_pv_eoi,enforce
> -smp 1,sockets=2,cores=2,maxcpus=4
> -device kvm64-x86_64-cpu,id=cpu2,socket-id=0,core-id=1,thread-id=0
> -device kvm64-x86_64-cpu,id=cpu3,socket-id=1,core-id=0,thread-id=0
> -device kvm64-x86_64-cpu,id=cpu4,socket-id=1,core-id=1,thread-id=0
> First core is not hotpluggable (-smp 1). (socket-id=0,core-id=0)
> Others cores are added with -device, with cpumodel,socket-id && core-id.
> cpuflags are defined globally in -cpu , and are auto applied on hotplug
> Tested with debian jessie, kernel 3.16.
> This new config is only apply with machine 2.7+cpu hotplug enabled, as it break live migration.
> pve-devel mailing list
> pve-devel at pve.proxmox.com
More information about the pve-devel