Description of problem: Pinning of emulator threads does not restrict live migration of a VM Version-Release number of selected component (if applicable): 4.12.2 How reproducible: Always Steps to Reproduce: 1. Set a VM with isolateEmulatorThread $ oc get vm fedora -o yaml | yq '.spec.template.spec.domain.cpu' dedicatedCpuPlacement: true isolateEmulatorThread: true 2. VM is not migratable because "VMI uses dedicated CPUs and emulator thread isolation" Additional info: * PR already exists by Marcelo: https://github.com/kubevirt/kubevirt/pull/9722/commits/feb0203f556b45a7fdcc58af4a9b5d6dde48c877
Verified on CNV-v4.12.4-56 VM with `isolateEmulatorThread: true` and `dedicatedCpuPlacement: true` can be succesfully migrated
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Virtualization 4.12.4 Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:3889
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days