Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
--------------------------
numa emulation won't check duplicate node id.
Version-Release number of selected component (if applicable):
-------------------------------------------------------------
qemu-kvm-rhev-1.5.3-50.el7.x86_64
How reproducible:
-------------------
100%
Steps to Reproduce:
----------------------
some negative test for numa:
1.
-numa node,mem=1024,cpus=0,nodeid=0 -numa node,mem=1024,cpus=1-2,nodeid=1 -numa node,mem=1024,cpus=2-3,nodeid=2
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) info numa
3 nodes
node 0 cpus: 0
node 0 size: 1024 MB
node 1 cpus: 1
node 1 size: 1024 MB
node 2 cpus: 2 3
node 2 size: 1024 MB
2.
-numa node,mem=1024,cpus=0,nodeid=0 -numa node,mem=1024,cpus=1-5,nodeid=1 -numa node,mem=1024,cpus=3,nodeid=2
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) info numa
3 nodes
node 0 cpus: 0
node 0 size: 1024 MB
node 1 cpus: 1 2
node 1 size: 1024 MB
node 2 cpus: 3
node 2 size: 1024 MB
3.
-numa node,mem=1024,cpus=0,nodeid=0 -numa node,mem=1024,cpus=1-5,nodeid=1 -numa node,mem=1024,cpus=3,nodeid=1
QEMU 1.5.3 monitor - type 'help' for more information
(qemu) info numa
3 nodes
node 0 cpus: 0
node 0 size: 1024 MB
node 1 cpus: 1 2 3
node 1 size: 1024 MB
node 2 cpus:
node 2 size: 0 MB
1 and 2 is tolerable, 3 may be a little trouble, in this case, guest only see one node(node 0), but this check can be done by high level tools like libvirt, so WONTFIX is also acceptable, that's why priority is low though severity is high.
Reproduce this bug as follow version:
Host:
qemu-kvm-rhev-1.5.3-60.el7ev.x86_64
Steps
1)Boot guest with numa nodes (nodeid has same number)
...-numa node,mem=1024,cpus=0,nodeid=0 -numa node,mem=1024,cpus=1-5,nodeid=1 -numa node,mem=1024,cpus=3,nodeid=1
Results:
guest can boot up
Verify this bus as follow version:
# uname -r
3.10.0-144.el7.x86_64
# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-2.1.0-2.el7.x86_64
Steps as same as reproduce
Results:
qemu-kvm: -numa node,mem=1024,cpus=3,nodeid=1: Duplicate NUMA nodeid: 1
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