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 cannot start when set numatune and disable cpuset in qemu.conf
Version-Release number of selected component (if applicable):
libvirt-1.2.17-2.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. disable cpuset in qemu.conf:
# vim /etc/libvirt/qemu.conf
cgroup_controllers = [ "devices", "blkio", "cpu", "cpuacct", "memory"]
2. restart libvirtd:
# service libvirtd restart
Redirecting to /bin/systemctl restart libvirtd.service
3. prepare a guest with numa settings:
# virsh numatune rhel7.0
numa_mode : strict
numa_nodeset : 0
# virsh start rhel7.0
error: Failed to start domain rhel7.0
error: internal error: Controller 'cpuset' is not mounted
Actual results:
guest cannot start when set numatune and disable cpuset in qemu.conf
Expected results:
guest can start success since the libnuma have some function for bind to a node , and we need check if cpuset is disabled then try to use it.
Additional info:
Also found this issue with setvcpus and iothreadadd:
# virsh setvcpus test4 3
error: internal error: Controller 'cpuset' is not mounted
# virsh iothreadadd test4 11
error: Requested operation is not valid: failed to set cpuset.cpus in cgroup for id 11
Comment 2Martin Kletzander
2015-08-03 11:24:20 UTC
Fixed upstream with v1.2.18-3-g1439eb32afc9:
commit 1439eb32afc9f97378d1d121c0b5c80d2f84896c
Author: Luyao Huang <lhuang>
Date: Mon Jul 20 17:18:37 2015 +0800
qemu: fix some api cannot work when disable cpuset in conf
Verify it as follows. The result is expected. Move its status to VERIFIED.
# rpm -q libvirt
libvirt-1.2.17-6.el7.x86_64
# cat /etc/libvirt/qemu.conf|grep cgroup_controllers
cgroup_controllers = [ "cpu", "devices", "memory", "blkio", "cpuacct" ]
# service libvirtd restart
Redirecting to /bin/systemctl restart libvirtd.service
# virsh start test4
Domain test4 started
# virsh numatune test4
numa_mode : strict
numa_nodeset : 1
# virsh iothreadadd test4 11
# virsh iothreadinfo test4
IOThread ID CPU Affinity
---------------------------------------------------
11 0-31
# virsh setvcpus test4 2
# virsh vcpucount test4
maximum config 4
maximum live 4
current config 1
current live 2
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