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.
Fixed upstream:
commit 638e3d270fc4b1ebeab0d139c2b4e54f590eb8b5
Author: Peter Krempa <pkrempa>
Date: Thu Feb 12 16:04:45 2015 +0100
conf: numa: Refactor logic in virDomainNumatuneParseXML
Shuffling around the logic will allow to simplify the code quite a bit.
As an additional bonus the change in the logic now reports an error if
automatic placement is selected and individual placement is configured.
v1.2.12-174-g638e3d2
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/RHBA-2015-2202.html
Description of problem: when there is no numatune for memory, 'auto' placement vcpu will add 'auto' placement memory numatune automatically. But user specified memnode for each guest NUMA node in numatune, when 'auto' placement vcpu without memory placement. The libvirtd will add memory placement to 'auto' and remove memnode. Although this configuration doesn't align vcpus, but it should be valid. Version-Release number of selected component (if applicable): libvirt-1.2.8-15.el7.x86_64 qemu-kvm-rhev-2.1.2-21.el7.x86_64 3.10.0-223.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. prepare guest xml # cat dummy.xml <domain type='qemu'> <name>dummy</name> <memory unit='KiB'>2097152</memory> <vcpu placement='auto'>4</vcpu> <numatune> <memnode cellid="0" mode="strict" nodeset="1"/> <memnode cellid="1" mode="preferred" nodeset="0"/> </numatune> <os> <type arch='x86_64' machine='pc'>hvm</type> </os> <cpu> <numa> <cell id='0' cpus='0-1' memory='1048576'/> <cell id='1' cpus='2-3' memory='1048576'/> </numa> </cpu> </domain> # virsh define dummy.xml 2. then check xml, the <memnode> is lost # virsh dumpxml dummy <domain type='qemu'> <name>dummy</name> <uuid>1fd33000-27cb-425c-94f9-c7454914acdb</uuid> <memory unit='KiB'>2097152</memory> <currentMemory unit='KiB'>2097152</currentMemory> <vcpu placement='auto'>4</vcpu> <numatune> <memory mode='strict' placement='auto'/> </numatune> <os> <type arch='x86_64' machine='pc-i440fx-rhel7.1.0'>hvm</type> <boot dev='hd'/> </os> <cpu> <numa> <cell id='0' cpus='0-1' memory='1048576'/> <cell id='1' cpus='2-3' memory='1048576'/> </numa> </cpu> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <controller type='usb' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </memballoon> </devices> </domain> Expect result: memnode is an other memory placement configuration, 'auto' vcpu placement should not remove it.