>>To be more specific, this is a general problem (not really related to >>maxcpus). >> >>If the user change setting during the VM is running many things can go wrong, >>for example >>live migration.
>>A simply solution would be to disable any modification which are not hotplug >>aware? Yes,I have thinked about this a long time ago. I think it currently confusing users, as we need to stop/start vm to get the modification work. I don't known if we need to disable online modification only in pve-manager ? or also command line/api ? (Maybe some external management interfaces need to change config online through api) ----- Mail original ----- De: "Dietmar Maurer" <[email protected]> À: "Dietmar Maurer" <[email protected]>, "Alexandre Derumier" <[email protected]>, [email protected] Envoyé: Mardi 14 Janvier 2014 07:44:45 Objet: RE: [pve-devel] [PATCH 3/3] forbid maxcpus change when vm is running > why can't we change maxcpus? To be more specific, this is a general problem (not really related to maxcpus). If the user change setting during the VM is running many things can go wrong, for example live migration. A simply solution would be to disable any modification which are not hotplug aware? _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
