Bug 893654
| Summary: | allow non-contiguous CPU ranges on -numa command-line options | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Eduardo Habkost <ehabkost> |
| Component: | qemu-kvm-rhev | Assignee: | Eduardo Habkost <ehabkost> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | bsarathy, ehabkost, hhuang, juzhang, michen, mkenneth, mrezanin, rbalakri, shuang, virt-maint, xfu |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | QEMU 2.1.0 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-03-05 09:42:06 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 883504 | ||
|
Description
Eduardo Habkost
2013-01-09 15:37:34 UTC
Unfortunately the mechanism to implement manual pinning of multi-node VMs is still under review upstream, and libvirt work to support the new mechanism will be possible only after the new mechanism gets in a QEMU release, so the manual pinning mechanism won't be in RHEL-7.0. New feature -- moving to qemu-kvm-rhev component. Patches were included upstream and will be in QEMU 2.1.0. Tested this bug with qemu-kvm-rhev-2.1.0-2.el7.x86_64. and Tested three scenarios. S1.Tested non-continues node. #/usr/libexec/qemu-kvm -M pc-i440fx-rhel7.0.0 -name RHEL-Server-7.0-64 -m 4G -smp 4,cores=2,threads=2,sockets=1,maxcpus=160 -numa node,cpus=0,2,4,12 result: qemu-kvm: -numa node,cpus=0,2,4,12: Invalid parameter '2 2. Tested continues nodes. #/usr/libexec/qemu-kvm -m 4G -smp 12,maxcpus=160 -numa node,cpus=0-5 -numa node,cpus=6-11 result(inside guest): # numactl -H available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 node 0 size: 2047 MB node 0 free: 1349 MB node 1 cpus: 6 7 8 9 10 11 node 1 size: 2047 MB node 1 free: 1592 MB node distances: node 0 1 0: 10 20 1: 20 10 3. Tested continues nodes. #/usr/libexec/qemu-kvm -m 6G -smp 18,maxcpus=160 -numa node,cpus=0-5 -numa node,cpus=6-11 -numa node,cpus=18-23 result(inside guest): # numactl -H available: 3 nodes (0-2) node 0 cpus: 0 1 2 3 4 5 12 13 14 15 16 17 node 0 size: 2047 MB node 0 free: 1220 MB node 1 cpus: 6 7 8 9 10 11 node 1 size: 2047 MB node 1 free: 1703 MB node 2 cpus: node 2 size: 2048 MB node 2 free: 1982 MB node distances: node 0 1 2 0: 10 20 20 1: 20 10 20 2: 20 20 10 Test summary For S1 result. seem qemu-kvm-rhev-2.1 don't support it. For S2 result. it is expect result. For S3 result. node 2 don't include anyone cpu. not sure if it is expect, As host only have two nodes. so it depend on host numa node number. right? Eduardo, would you please take a look at this test result? seem this bug is not fixed. If my understanding is wrong. please correct me. Another, This is host numa architecture. # numactl -H available: 2 nodes (0-1) node 0 cpus: 0 1 2 3 4 5 12 13 14 15 16 17 node 0 size: 12253 MB node 0 free: 8453 MB node 1 cpus: 6 7 8 9 10 11 18 19 20 21 22 23 node 1 size: 16383 MB node 1 free: 14073 MB node distances: node 0 1 0: 10 20 1: 20 10 (In reply to FuXiangChun from comment #8) > Tested this bug with qemu-kvm-rhev-2.1.0-2.el7.x86_64. and Tested three > scenarios. > > S1.Tested non-continues node. > #/usr/libexec/qemu-kvm -M pc-i440fx-rhel7.0.0 -name RHEL-Server-7.0-64 -m 4G > -smp 4,cores=2,threads=2,sockets=1,maxcpus=160 -numa node,cpus=0,2,4,12 > > result: > qemu-kvm: -numa node,cpus=0,2,4,12: Invalid parameter '2 That's not how it works. The right format is: "cpus=0,cpus=2,cpus=4,cpus=12". > 3. Tested continues nodes. > #/usr/libexec/qemu-kvm -m 6G -smp 18,maxcpus=160 -numa node,cpus=0-5 -numa > node,cpus=6-11 -numa node,cpus=18-23 You have only 18 VCPUs (0-17), and you are trying to assign offline (unplugged) VCPUs 18-23 to node 2. numactl will show only the online CPUs. You forgot to assign VCPUs 11-17. > Test summary > For S1 result. > seem qemu-kvm-rhev-2.1 don't support it. The syntax is incorrect. > > For S2 result. > it is expect result. Correct. > > For S3 result. > node 2 don't include anyone cpu. not sure if it is expect, As host only have > two nodes. so it depend on host numa node number. right? The guest NUMA topology has absolutely nothing to do with the host topology, and depend solely on the QEMU command-line options. According to comment 10. Re-tested S1 and S3. S1. Boot guest with -smp 6,...-numa node,cpus=0,cpus=2,cpus=4,cpus=17,cpus=11,cpus=22 got guest numa topology inside guest. # numactl -H available: 1 nodes (0) node 0 cpus: 0 1 2 3 4 5 node 0 size: 27647 MB node 0 free: 25965 MB node distances: node 0 0: 10 S3. Boot guest with -m 27G -smp 24,maxcpus=160 \ -numa node,cpus=0-5 -numa node,cpus=6-11 -numa node,cpus=12-17 -numa node,cpus=18-23 \ Got numa topology inside guest. # numactl -H available: 4 nodes (0-3) node 0 cpus: 0 1 2 3 4 5 node 0 size: 6911 MB node 0 free: 6239 MB node 1 cpus: 6 7 8 9 10 11 node 1 size: 6912 MB node 1 free: 6450 MB node 2 cpus: 12 13 14 15 16 17 node 2 size: 6912 MB node 2 free: 6625 MB node 3 cpus: 18 19 20 21 22 23 node 3 size: 6912 MB node 3 free: 6585 MB node distances: node 0 1 2 3 0: 10 20 20 20 1: 20 10 20 20 2: 20 20 10 20 3: 20 20 20 10 According to comment 10, This is expect result. Base on test result of S1 S2 and S3. this bug is fixed. 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://rhn.redhat.com/errata/RHSA-2015-0624.html |