Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-755

Incorrect CPU affinity with numatune mode strict

    • None
    • None
    • rhel-sst-virtualization
    • ssg_virtualization
    • 5
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • If docs needed, set a value
    • None

      Description of problem:
      We have been trying to set the NUMA affinity of specific VM using libvirt by adding this into the VM config:
      <numatune>
      <memory mode='strict' nodeset='1'/>
      </numatune>
      This should set the correct memory and vcpu affinity to a specific NUMA node. The memory affinity was right:
      PID Node 0 Node 1 Node 2 Node 3 Node 4 Node 5 Node 6 Node 7 Total
      --------------- ------ ------ ------ ------ ------ ------ ------ ------ -----
      7103 (qemu-kvm) 0 2126 2 2 2 2 1 2 2198

      However, the emulator and vcpus have set affinity to a different NUMA node:

      1. taskset -cp 7103
        pid 7103's current affinity list: 12-15,44-47

      Version-Release number of selected component (if applicable):
      libvirt-8.5.0-7.el9_1.x86_64

      How reproducible:
      always

      Steps to Reproduce:
      1. Install hypervisor with RHEL9.1.0 and virtualization packages
      2. Install VM
      3. Add this into the VM config:
      <numatune>
      <memory mode='strict' nodeset='1'/>
      </numatune>
      <vcpu placement='auto'>8</vcpu>

      4. Start VM
      5. Check memory affinity using numastat -c qemu-kvm
      6. Check CPU affinity using taskset -cp <PID>

      Actual results:
      Correct memory, but incorrect CPU affinity.

      Expected results:
      Correct memory and CPU affinity list.

      Additional info:
      We can provide you with a hypervisor with many NUMA nodes for further investigation of this issue.

              virt-maint virt-maint
              rhn-support-atomasov Adrian Tomasov
              virt-maint virt-maint
              Liang Cong Liang Cong
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: