This bug was initially created as a copy of Bug #2198976 I am copying this bug because: 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
Fix is in, https://github.com/kubevirt/kubevirt/pull/9941
verify with build: CNV-v4.13.3.rhel9-160 step: 1: create vm with: ... domain: cpu: dedicatedCpuPlacement: true isolateEmulatorThread: true ... 2: start vm and do live migration $ oc get virtualmachineinstancemigrations.kubevirt.io NAME PHASE VMI vm-fedora-migration-jwyya Succeeded vm-fedora migration succeeded move to verified.
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 (Important: OpenShift Virtualization 4.13.3 Images security and bug fix update), 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/RHSA-2023:4664