** Summary changed: - qemuProcessSetEmulatorAffinity() called before emulator process actually running + qemuProcessSetEmulatorAffinity() not behaving as expected
** Description changed: When running on a 24-CPU host and using vCPU and emulator pinning I've seen cases where the specified emulator pinning isn't applied as expected. - It appears the bug was introduced by 411cea6 which moved both + It appears the bug was introduced/uncovered by 411cea6 which moved both qemuSetupCgroupForEmulator() and qemuProcessSetEmulatorAffinity() up before the call to qemuProcessWaitForMonitor(). Reverting this commit makes the problem go away. + + It's not obvious why this makes a difference, since the pid had to have + been up and running already. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1441781 Title: qemuProcessSetEmulatorAffinity() not behaving as expected Status in QEMU: New Bug description: When running on a 24-CPU host and using vCPU and emulator pinning I've seen cases where the specified emulator pinning isn't applied as expected. It appears the bug was introduced/uncovered by 411cea6 which moved both qemuSetupCgroupForEmulator() and qemuProcessSetEmulatorAffinity() up before the call to qemuProcessWaitForMonitor(). Reverting this commit makes the problem go away. It's not obvious why this makes a difference, since the pid had to have been up and running already. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1441781/+subscriptions