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

Alexandre DERUMIER aderumier at odiso.com
Fri Jan 23 07:46:46 CET 2015

about memory,

currently I define 

to enable hotplug,
-m size=<memory>,slots=255,maxmem=<maxmemory>M

maybe could we define a big maxmem value by default (like 2TB),
to remove this option.

I don't known if 
-m size=<memory>,slots=255,maxmem=<maxmemory>M 
-m size=<memory>,

break migration 

----- Mail original -----
De: "Stefan Priebe" <s.priebe at profihost.ag>
À: "dietmar" <dietmar at proxmox.com>
Cc: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Vendredi 23 Janvier 2015 07:03:00
Objet: Re: [pve-devel] qemu-server : cpu hotplug rework

Am 23.01.2015 um 06:54 schrieb Dietmar Maurer <dietmar at proxmox.com>: 

>>>> 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) 
> Do you know if CPU topology information is included in live migration data 
> stream? 
> Or do we need to start the VM with exactly the same topology on the other side? 

It's not included. It's the same with the plugged dimm modules. You must start the vm exactly with the current topology and dimm count/ plugged dimms. 


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