From: Launchpad Bug Tracker <1821771@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1821771] Re: KVM guest does not reflect numa distances configured through qemu
Date: Mon, 05 Jul 2021 04:17:32 -0000 [thread overview]
Message-ID: <162545865224.12677.8484381871430887108.malone@loganberry.canonical.com> (raw)
In-Reply-To: 155361583469.17984.11681376513113338670.malonedeb@gac.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821771
Title:
KVM guest does not reflect numa distances configured through qemu
Status in QEMU:
Expired
Bug description:
KVM guest does not reflect numa distances configured through qemu
Env:
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 stdbool.h.
FALSE and TRUE (with capital letters) are the constants defined by glib for
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 <stdbool.h>).
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.
qemu-commandline:
/usr/share/avocado-plugins-vt/bin/install_root/bin/qemu-system-ppc64 -name guest=vm2,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-15-vm2/master-key.aes -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 file=/var/lib/avocado/data/avocado-vt/images/jeos-27-ppc64le.qcow2,format=qcow2,if=none,id=drive-scsi0-0-0-0 -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,device_id=drive-scsi0-0-0-0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=30,id=hostnet0,vhost=on,vhostfd=31 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:f4:f5:f6,bus=pci.0,addr=0x1 -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
/proc/device-tree/cpus/PowerPC,POWER8@0/ibm,associativity
00000005 00000000 00000000 00000000 00000000 00000000
/proc/device-tree/cpus/PowerPC,POWER8@10/ibm,associativity
00000005 00000000 00000000 00000000 00000001 00000010
/proc/device-tree/cpus/PowerPC,POWER8@18/ibm,associativity
00000005 00000000 00000000 00000000 00000001 00000018
/proc/device-tree/cpus/PowerPC,POWER8@8/ibm,associativity
00000005 00000000 00000000 00000000 00000000 00000008
# lsprop /proc/device-tree/rtas/ibm,associativity-reference-points
/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:
https://bugs.launchpad.net/qemu/+bug/1821771/+subscriptions
prev parent reply other threads:[~2021-07-05 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <155361583469.17984.11681376513113338670.malonedeb@gac.canonical.com>
2020-08-03 12:24 ` [Bug 1821771] Re: KVM guest does not reflect numa distances configured through qemu Satheesh Rajendran
2021-05-05 17:41 ` Thomas Huth
2021-07-05 4:17 ` Launchpad Bug Tracker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162545865224.12677.8484381871430887108.malone@loganberry.canonical.com \
--to=1821771@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.