Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-64861

CPU socket is not updated inside the VM after CPU hotplug

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • CNV Virtualization
    • None
    • Quality / Stability / Reliability
    • 0.42
    • False
    • Hide

      None

      Show
      None
    • 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:

      
      

              tnisan@redhat.com Tal Nisan
              gouyang1@redhat.com Guohua Ouyang
              Kedar Bidarkar Kedar Bidarkar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: