Starting 4.16, CPU hotplug was denied when the VM had VM.spec.template.spec.domain.devices.networkInterfaceMultiQueue set to `true`.

This limitation was removed in 4.20.0, 4.19.0, 4.18.z (but still exists in 4.17.z and 4.16.z).

A note should be added with the following details:
- On a CPU hotplug scenario, the VM owner will certainly gain the benefit of the additional vCPUs. However, any network interfaces that were already present before the CPU hotplug will retain their initial queue count.
This is a characteristic of the underlying virtualization technology.

- If the VM owner would like the network interface queue count to align with the new vCPU configuration to maximize performance, a restart of the VM will be required. Of course, this decision is entirely up to the VM owner.
- Any new virtio network interfaces hotplugged after the CPU hotplug - will automatically have their queue count configured to match the updated vCPU configuration.

4.20.0, 4.19.0, 4.18.z

100%

1.
2.
3.