[pve-devel] qemu-server : cpu hotplug rework

Alexandre DERUMIER aderumier at odiso.com
Fri Jan 23 05:44:30 CET 2015


please note that  qemu interface for cpu hotplug will change soon,

with device_add|device_del   instead cpu_add.


(I'm not sure it'll break think).


some libvirt patches are available to handle
http://www.mail-archive.com/libvir-list@redhat.com/msg107332.html


qemu patches for cpu hotplug|unplug


[RESEND PATCH v1 0/5] Common unplug and unplug request cb for memory and CPU 
https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg00429.html
[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
[PATCH v2 00/11] cpu: add i386 cpu hot remove support
https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg01557.html

----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "dietmar" <dietmar at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 23 Janvier 2015 05:17:25
Objet: Re: [pve-devel] qemu-server : cpu hotplug rework

>>Or should we simply assume 'vcpus' is the switch to enable hotplug? 
Yes, I thinked at something like this. 

On gui, on processor form, 

maybe can we replace the "total cores: x" text, by a numberfield (vcpus) 

"total enabled cores: x" 

-default is (sockets * cores) 


I'll try to see how it's implemented in vmware, xen, ovirt ... 



>>We could do the same for memory hotplug, and disable it if 'dimm_memory' is 
>>not defined inside config? 

For memory hotplug, we need to define "maxmemory" option to enable dimm hotplug 



----- Mail original ----- 
De: "dietmar" <dietmar at proxmox.com> 
À: "aderumier" <aderumier at odiso.com> 
Cc: "pve-devel" <pve-devel at pve.proxmox.com> 
Envoyé: Jeudi 22 Janvier 2015 19:31:24 
Objet: Re: [pve-devel] qemu-server : cpu hotplug rework 

> > > maybe do you don't have define vcpus ? 
> > 
> > vcpus is not set when you create a VM using the GUI. 
> > 
> > This leads to the situation that CPU hotplug is disabled by default. 
> > 
> > Any ideas how to improve that situation? 
> 
> Can we simply use topology from host on create? 
> 
> # qm create 100 --vcpus 3 
> 
> Above command use socket/cores from host, so the resulting config is 
> 
> vcpus: 3 
> sockets: 2 
> cores: 4 
> 
> What do you think? 

Or should we simply assume 'vcpus' is the switch to enable hotplug? 
We could do the same for memory hotplug, and disable it if 'dimm_memory' is 
not defined inside config? 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 


More information about the pve-devel mailing list