-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
Description of problem:
CPU socket is not updated inside the VM after CPU hotplug
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a VM with 2 CPU from bootable volume or template from UI 2. Go to VM's configuration tab 3. Increase the CPU number from 2 to 3 4. Go to VM yaml tab, the socket value is updated in the yaml 5. Wait for VM migrate complete 6. Login the VM and check the socket number via lscpu 7. The socket number is 2, but the CPU(s) is updated to 3 8. Restart the VM 9. The socket number is 3.
Actual results:
The socket number is not updated.
Expected results:
The socket is updated correctly via CPU hotplug
Additional info:
- is blocked by
-
CNV-62851 [Tracker Bug] [vcpu hotplug] the cpu is offline after migration successfully
-
- New
-