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

Alexandre DERUMIER aderumier at odiso.com
Fri Jan 23 05:17:25 CET 2015


>>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? 



More information about the pve-devel mailing list