> 1.) Block changes on a running VM through API - except hotplug is enabled > and the change is hotpluggable
OK for me. > 2.) What about CPU? You don't need the hotplug feature for this. Right now > you need to manual add maxcpu setting to the conf. To have it straight i > would like to also only enable this if hotplug is set to 1 The goal is to make hotplug the default. It is just disabled because it is unstable for some features. > 3.) I would like to store the generated command line of each start in the > command file to be sure at restore or migration the exact and correct > command line is used I don't think that we should use that (as explained in the previous mail). > 4.) For hot pluggable memory there is a way to get everything out of qom- > list and qom-get (sadly around 20 qom queries for each dimm / memdev). > Or to store memory / dimm adds in temporarily in config file until a vm is > newly started. I would disable hotplup for that until it can be solved. _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
