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:
guest NUMA cannot start when automatic NUMA placement.
From the doc, only memnode is conflict with automatic NUMA placement,
if <numa> <cell> also not compatible with automatic NUMA placement,
an error in parse phase would be better, just like that for memnode.
Version-Release number of selected component (if applicable):
libvirt-1.2.8-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. prepare NUMA host, and add config to a guest:
# virsh edit r7
...
<memory unit='KiB'>1048576</memory>
<vcpu placement='auto'>4</vcpu>
<numatune>
<memory mode='strict' placement='auto'/>
</numatune>
<cpu>
<numa>
<cell id='0' cpus='0-1' memory='524288'/>
<cell id='1' cpus='2-3' memory='524288'/>
</numa>
</cpu>
...
2. start it
# virsh start r7
error: Failed to start domain r7
error: internal error: Advice from numad is needed in case of automatic
numa placement
Expect result:
if <numa> <cell> also not compatible with automatic NUMA placement,
an error in parse phase would be better, just like that for memnode.
Actual result:
failed to start.
Comment 3Martin Kletzander
2014-10-30 06:36:21 UTC
Well, you're right. If someone wants to have guest NUMA nodes, he's much better off using static placement as automatic will most likely cause performance drop. Anyway, it should still be available to those who are using it already.
Comment 4Martin Kletzander
2014-11-04 09:53:01 UTC
Fixed upstream by v1.2.10-2-g11a4875:
commit 11a48758a7d6c946062c130b6186ae3eadd58e39
Author: Martin Kletzander <mkletzan>
AuthorDate: Thu Oct 30 07:34:30 2014 +0100
qemu: make advice from numad available when building commandline
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-0323.html
description of problem: guest NUMA cannot start when automatic NUMA placement. From the doc, only memnode is conflict with automatic NUMA placement, if <numa> <cell> also not compatible with automatic NUMA placement, an error in parse phase would be better, just like that for memnode. Version-Release number of selected component (if applicable): libvirt-1.2.8-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepare NUMA host, and add config to a guest: # virsh edit r7 ... <memory unit='KiB'>1048576</memory> <vcpu placement='auto'>4</vcpu> <numatune> <memory mode='strict' placement='auto'/> </numatune> <cpu> <numa> <cell id='0' cpus='0-1' memory='524288'/> <cell id='1' cpus='2-3' memory='524288'/> </numa> </cpu> ... 2. start it # virsh start r7 error: Failed to start domain r7 error: internal error: Advice from numad is needed in case of automatic numa placement Expect result: if <numa> <cell> also not compatible with automatic NUMA placement, an error in parse phase would be better, just like that for memnode. Actual result: failed to start.