Importing a multi-CPU/VT-x VM on a non-VTx host makes changing VM settings impossible => Fixed in SVN

[Socratis]

Assume you have a VM with multiple CPUs, or a VM that has VT-x enabled in the settings. Copy VM folder (.vbox, VDIs, Snapshots and Logs) to a host that does not have VT-x available. Add the VM. Since there's no VT-x on the host:

• The System » Acceleration settings become disabled.
• The CPU count drops to 1. In the GUI.

Problem is that neither the "hwvirtex" changes, nor the number of CPUs. End result? Can't start the VM (<VERR_VMX_NO_VMX>), can't change the VM settings, at least via the GUI (hence the "GUI" component selected).

The logic needs to change so that things do not become disabled, they become "flagged". I would go to the path/logic followed by the "2D acceleration" setting in a non-Windows VM.

1. Flag it (yellow triangle, warning/error notification)
2. (Optional) Force-modify the settings to what's acceptable/allowed, just like 2D is disabled (even when selected) in a non-Windows VM. 1 CPU, no VT-x.

I'm leaving open the second option, just like the amount of CPU/RAM settings are flagged, but not force-modified. If someone wants to be greeted by an error, fine by me.

No VM logs (for obvious reasons) but if you want a .vbox, please say so.

[gombara]

Fixed in the development branch by r72481 and r72467.

[Socratis]

Presumably? Build me a test build, and I will gladly test it. The proof of the pudding is in the eating... :D

PS. Same goes for #17781 and #17815...