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:
A machine with an invalid CPU set - out of the range of available host cpus - starts successfully but is expected to fail. This seemingly happens inconsistently on a specific host with a specific number of CPUs and doesn't reproduce on other archs or s390x hosts where two different error messages are displayed and the machines wouldn't start (as expected).
Version-Release number of selected component (if applicable):
libvirt-8.9.0-2.el9.s390x
kernel-5.14.0-197.el9.s390x
How reproducible:
100% on specific s390x host
Steps to Reproduce:
1. On a host with 12 CPUs (value "CPU(s)" from lscpu|grep CPU), define a domain with cpu set out of range, e.g.
<vcpu cpuset="0-12,^2" current="3" placement="static">8</vcpu>
or equivalently
<vcpu cpuset="0-1,3-12" current="3" placement="static">8</vcpu>
2. Try to start the vm
Actual results:
The VM starts successfully
Expected results:
The VM doesn't start, instead there's an error message from cgroups "Numerical result out of range"
Additional info:
A) Yingshun confirmed the expected result on x86_64.
B) In the reported case we see cgroup values
# cat /sys/fs/cgroup/machine.slice/machine-qemu\\x2d1\\x2davocado\\x2dvt\\x2dvm1.scope/libvirt/emulator/cpuset.cpus
0-1,3-12
# cat /sys/fs/cgroup/machine.slice/machine-qemu\\x2d1\\x2davocado\\x2dvt\\x2dvm1.scope/libvirt/emulator/cpuset.cpus.effective
0-1,3-11
C) On another s390x host with 4 CPUs and the same component versions, this can't be reproduced, instead another error message is showing. With
<vcpu placement='static' cpuset='0-4,^2' current='3'>4</vcpu>
we get an error message
error: Invalid value '0-1,3-4' for 'cpuset.cpus': Invalid argument
Boris, could you please have a look at this issue?
Comment 3RHEL Program Management
2023-10-05 09:24:55 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 4RHEL Program Management
2023-10-05 09:26:05 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.