On 02/11/2018 17:54, Daniel P. Berrangé wrote: > We have usually followed a rule that new machine types must not > affect runability of a VM on a host. IOW new machine types should > not introduce dependancies on specific kernels, or hardware features > such as CPU flags.
> Anything that requires a new kernel feature thus ought to be an > opt-in config tunable on the CLI, separate from machine type > choice. Unless someone tinkered with the module parameters, they could not even use nested virtualization before 4.20. So for everyone else, "-cpu ...,+vmx" does count as an "opt-in config tunable on the CLI" that requires 4.20. For those that did tinker with module parameters, we can grandfather in the old machine types, so that they can use nested virtualization with no live migration support. For those that did not, however, I don't think it makes sense to say "oh by the way I really want to be able to migrate this VM" on the command line, or even worse on the monitor. Paolo > Alternatively in this case, it could potentially be a > migration parameter settable via QMP. QEMU on each side could > advertize whether the migration parameter is available, and > the mgmt app (which can see both sides of the migration) can > then decide whether to enable it.
