[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 1821771] Re: KVM guest does not reflect numa distances configured t

From: Satheesh Rajendran
Subject: [Bug 1821771] Re: KVM guest does not reflect numa distances configured through qemu
Date: Mon, 03 Aug 2020 12:24:56 -0000

Documentation describing the current qemu behaviour is captured here,

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  KVM guest does not reflect numa distances configured through qemu

Status in QEMU:

Bug description:
  KVM guest does not reflect numa distances configured through qemu

  Host/Guest Kernel: 5.1.0-rc1-g72999bbdc
  qemu : 3.1.90 (v2.8.0-rc0-18614-g278aebafa0-dirty) [repo: 
https://github.com/dgibson/qemu; branch:ppc-for-4.1 ]
  # git log -1
  commit 278aebafa02f699857ca082d966bcbc05dc9bffb (HEAD -> ppc-for-4.1)
  Author: Jafar Abdi <cafer.abdi@gmail.com>
  Date:   Sat Mar 23 17:26:36 2019 +0300

      tests/libqos: fix usage of bool in pci-spapr.c
      Clean up wrong usage of FALSE and TRUE in places that use "bool" from 
      FALSE and TRUE (with capital letters) are the constants defined by glib 
      being used with the "gboolean" type of glib. But some parts of the code 
also use
      TRUE and FALSE for variables that are declared as "bool" (the type from 
      Signed-off-by: Jafar Abdi <cafer.abdi@gmail.com>
      Reviewed-by: Eric Blake <eblake@redhat.com>
      Message-Id: <1553351197-14581-4-git-send-email-cafer.abdi@gmail.com>
      Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

  # libvirtd -V
  libvirtd (libvirt) 5.1.0

  Steps to reproduce:
  1. Boot attached guest xml with predefined numa distance.

  /usr/share/avocado-plugins-vt/bin/install_root/bin/qemu-system-ppc64 -name 
guest=vm2,debug-threads=on -S -object 
 -machine pseries-4.0,accel=kvm,usb=off,dump-guest-core=off -m 4096 -realtime 
mlock=off -smp 4,sockets=1,cores=4,threads=1 -numa 
node,nodeid=0,cpus=0-1,mem=2048 -numa node,nodeid=1,cpus=2-3,mem=2048 -uuid 
1a870f1d-269a-4a8c-84bc-2b5bda72823a -display none -no-user-config -nodefaults 
-chardev socket,id=charmonitor,fd=28,server,nowait -mon 
chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot 
strict=on -kernel /home/kvmci/linux/vmlinux -append root=/dev/sda2 rw 
console=tty0 console=ttyS0,115200 init=/sbin/init  initcall_debug selinux=0 
-device qemu-xhci,id=usb,bus=pci.0,addr=0x3 -device 
virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x2 -drive 
 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device 
-chardev pty,id=charserial0 -device 
spapr-vty,chardev=charserial0,id=serial0,reg=0x30000000 -device 
virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on

  2. Check numa distance and other details inside guest
  # numactl -H
  available: 2 nodes (0-1)
  node 0 cpus: 0 1
  node 0 size: 2025 MB
  node 0 free: 1837 MB
  node 1 cpus: 2 3
  node 1 size: 2045 MB
  node 1 free: 1646 MB
  node distances:
  node   0   1 
    0:  10  40 -----------------------------------NOK
    1:  40  10 

  # lsprop /proc/device-tree/cpus/PowerPC\,POWER9\@*/ibm\,associativity 
                 00000005 00000000 00000000 00000000 00000000 00000000
                 00000005 00000000 00000000 00000000 00000001 00000010
                 00000005 00000000 00000000 00000000 00000001 00000018
                 00000005 00000000 00000000 00000000 00000000 00000008

  # lsprop /proc/device-tree/rtas/ibm,associativity-reference-points
                 00000004 00000004

  Expected numa distances:
  node distances:
  node   0   1 
    0:  10  20
    1:  20  10

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]