When attempting to live update a virtual machine (VM), if the instance type has a spec.domain.maxSockets value smaller than spec.domain.sockets, the expected error message—"Socket value set higher than max value!"—does not appear until the VM is restarted, and the VM is on a stopped stage.

* This highlights a broader issue: it's currently possible to create an instance type configuration that is known to be invalid from the start for example

maxSockets: 6
sockets: 8

4.19

100%

1. Create a VM with an instance type and start it
2. Create an instance type with maxSockets smaller then sockets

The VM will keep running as normal without any error, until it is restarted

Some type of error should be present.