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.

Bug 1035955

Summary: Need better error message for NUMA memory tuning
Product: Red Hat Enterprise Linux 7 Reporter: Jincheng Miao <jmiao>
Component: libvirtAssignee: Michal Privoznik <mprivozn>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 7.0CC: acathrow, dyuan, gsun, honzhang, mzhan, zhwang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-1.1.1-15.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-13 10:24:08 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 Jincheng Miao 2013-11-29 02:43:03 UTC
Description of problem:
It needs a better error message when detecting a error for NUMA memory tuning.

Version-Release number of selected component (if applicable):
libvirt-1.1.1-13.el7.x86_64
qemu-kvm-rhev-1.5.3-20.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. define a guest with two preferred nodes, as we known it is wrong:
# virsh edit kvm-rhel6.5-x86_64-qcow2-virtio
...
  <vcpu placement='static'>3</vcpu>
  <numatune>
    <memory mode='preferred' nodeset='2-3'/>
  </numatune>
...

2. start it, we cann't see the real error
# virsh start kvm-rhel6.5-x86_64-qcow2-virtio
error: Failed to start domain kvm-rhel6.5-x86_64-qcow2-virtio
error: Child quit during startup handshake: Input/output error

3. check out qemu.log
# tail /var/log/libvirt/qemu/kvm-rhel6.5-x86_64-qcow2-virtio.log
libvirt:  error : internal error: NUMA memory tuning in 'preferred' mode only supports single node

Actual results:
error message is hide in qemu.log

Expected results:
show error message when virsh return.

Comment 2 Michal Privoznik 2013-12-03 17:53:11 UTC
Patch proposed upstream:

https://www.redhat.com/archives/libvir-list/2013-December/msg00210.html

Comment 5 Jincheng Miao 2013-12-16 04:20:14 UTC
This fix is verified on libvirt-1.1.1-15.el7:
# virsh edit virt-tests-vm1
...
  <vcpu placement='static'>3</vcpu>
  <numatune>
    <memory mode='preferred' nodeset='2-3'/>
  </numatune>
...

# virsh start virt-tests-vm1
error: Failed to start domain virt-tests-vm1
error: internal error: Process exited prior to exec: libvirt:  error : internal error: Nodeset is out of range, host cannot support NUMA node bigger than 3

So I change the status to VERIFIED.

Comment 6 Ludek Smid 2014-06-13 10:24:08 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.