[pve-devel] Adding maxcpu breaks migration

[Stefan Priebe - Profihost AG]

Am 19.02.2014 07:46, schrieb Alexandre DERUMIER:
> Hi, you need to reboot the guest to have the maxcpu apply.
>
> If not, you have your source vm without running maxcpu, and target vm starting with maxcpu.
> So it's failing.

Sure. I was just thinking about preventing this issue. I think the main
problem of proxmox here is that is build a new start line from scratch.

Why don't we save the last start line in conf file and simply reuse that
one for migration?

Just for hotplug we need to modify that one.

Or we need need to grep that values using qmp commands to create a
correct line.

> That's why we have discusted in the mailing about to find a way to block change of non "hotplugable / hot change" values in pve-manager.

How do others fix this problem? libvirt and co.? Do you know that?

Stefan

> 
> ----- Mail original ----- 
> 
> De: "Stefan Priebe - Profihost AG" <s.priebe at profihost.ag> 
> À: "pve-devel" <pve-devel at pve.proxmox.com> 
> Envoyé: Mercredi 19 Février 2014 07:21:20 
> Objet: [pve-devel] Adding maxcpu breaks migration 
> 
> 
> Hello, 
> 
> 
> I've added maxcpu setting to all qemu conf's. 
> 
> 
> But then all migrations from machines still booted without will fail. Any ideas how to solve this? 
> 
> Greets, 
> Stefan 
> 
> 
> Excuse my typo s ent from my mobile phone. 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel at pve.proxmox.com 
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
>