-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
False
-
False
-
CLOSED
-
CNV-7860 - GA: Live migration with shared storage for work intensive workloads
-
Undefined
-
-
CNV SSP Sprint 204, CNV SSP Sprint 205, CNV SSP Sprint 207, CNV SSP Sprint 208, CNV Virtualization Sprint 210, CNV Virtualization Sprint 211, CNV Virtualization Sprint 212, CNV Virtualization Sprint 213, CNV Virtualization Sprint 214
-
High
-
None
Description of problem:
A VM with enabled CPU pinning will pin it's CPUs to (likely) the wrong CPU set after a migration.
When the VM is started it is getting set (A) of cores to pin to and will do so.
After migration the VM will get a different set (B), the pinning would need to be re-done, but this is not the case today.
Version-Release number of selected component (if applicable):
2.6
How reproducible:
always
Steps to Reproduce:
1. VM with pinning enabled
2. Live migrated
3. Check if VM is pinend to the new CPU set
Actual results:
It is not pinned to the new CPU set, it is pinned to the old
Expected results:
It is pinend to the new CPU set
Additional info:
