Bug 1377063
Summary: | Guest numa topology not correct after hot plug-unplug-plug vcpus | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Luyao Huang <lhuang> |
Component: | qemu-kvm-rhev | Assignee: | Igor Mammedov <imammedo> |
Status: | CLOSED ERRATA | QA Contact: | Yumei Huang <yuhuang> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | chayang, dzheng, ehabkost, imammedo, jinzhao, juzhang, knoel, mrezanin, virt-maint, xfu, yuhuang, zhguo |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | qemu-2.8 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 23:34:44 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Luyao Huang
2016-09-18 06:54:05 UTC
Fix has been posted during 2.7 merge windows but somehow fell through the cracks. I'll rebase and try to merge it into 2.8. Moving it to 7.4 as it's too late for 7.3 and it's not regression as it's been always that way. More exactly it's guest kernel issue as it forgets mapping info from SRAT, but since it's not fixable in old guests we can workaround it from QEMU side providing dynamic mapping via per cpu _PXM method. Fixed upstream in qemu-2.8: commit 271119313 acpi: provide _PXM method for CPU devices if QEMU is started numa enabled. Pls, retest once rebase to 2.8 is complete. [1] qemu command /usr/libexec/qemu-kvm \ -machine pc \ -nodefaults -rtc base=utc \ -m size=1048576k,slots=16,maxmem=15243264k \ -realtime mlock=off \ -smp 1,maxcpus=10,sockets=10,cores=1,threads=1 \ -numa node,nodeid=0,cpus=0,cpus=2-5,mem=512 \ -numa node,nodeid=1,cpus=1,cpus=6-9,mem=512 \ -object memory-backend-ram,id=memdimm0,size=134217728 \ -device pc-dimm,node=0,memdev=memdimm0,id=dimm0 \ -enable-kvm \ -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \ -k en-us \ -nodefaults \ -serial unix:/tmp/serial0,server,nowait \ -boot menu=on \ -qmp tcp:0:6666,server,nowait \ -vga qxl \ -chardev file,path=/home/seabios.log,id=seabios -device isa-debugcon,chardev=seabios,iobase=0x402 \ -drive file=/home/jinzhao/rhel7.qcow2,if=none,id=drive-virtio-disk0,format=qcow2,cache=none,werror=stop,rerror=stop \ -device virtio-blk-pci,drive=drive-virtio-disk0,id=virtio-disk0 \ -device virtio-net-pci,netdev=tap10,mac=9a:6a:6b:6c:6d:6f -netdev tap,id=tap10 \ -monitor stdio \ -vnc :0 \ Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392 |