some of my VMs need nested virtualization. I have added
to the KVM/raw data section of the VM template. This works until I migrate the VM (e.g. using
onehost flush for host maintenance). VMs with this option crash or lock up when migrated to host with a different CPU model.
Is there any way how to tell the scheduler that the particular guest can be migrated only to hosts with the same CPU?
I don’t want to bind such a guest to a particular CPU type (i.e. to a particular set of hosts), I just want to keep it on hosts with the same CPU as the host where the guest was originally created.