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.
Can reproduce this bug with qemu-kvm-8.0.0-10.el9.x86_64
Reproduce steps: Boot a q35 + ovmf guest with 448 vcpus
host version:
qemu-kvm-8.0.0-10.el9.x86_64
kernel-5.14.0-349.el9.x86_64
edk2-ovmf-20230524-2.el9.noarch
guest: rhel9.3.0
Yiqian Wei,
what on host are running this test? (I'm interested in lscpu command output)
and also lscpu from guest (I see mwait_idle in trace but don't see in script an option that enables mwait feature)
Hi Yiqian,
I see nothing suspicious about host.
Lets try to narrow down possible places to look at.
Can you try to following variants (only one thing at a time):
1. try find maxcpus at which problem starts to appear
2. try with 'idle=nomwait' in guest's kernel command line
3. try older (9.2) host/guest kernels
4. try with older QEMU (from RHEL.9.2)
Hi Yiqian,
Like Vitaly said bisection is the next logical step to finding out the offending patch.
Can you lend me machine you reproduce this issue on?
(In reply to Igor Mammedov from comment #14)
> Hi Yiqian,
>
> I see nothing suspicious about host.
> Lets try to narrow down possible places to look at.
>
> Can you try to following variants (only one thing at a time):
> 1. try find maxcpus at which problem starts to appear
It is not possible to determine the specific cpu, just the process of hotplug 416 vcpus.
> 2. try with 'idle=nomwait' in guest's kernel command line
With 'idle=nowait' in guest's kernel, can reproduce this bug with hotplug 416 vcpus.
> 3. try older (9.2) host/guest kernels
NOT reproduce this bug when hotplug 416 vcpus with kernel-5.14.0-284.28.1.el9_2. x86_64, but hit Bug 2118240 when reboot after hotplug 416 vcpus.
> 4. try with older QEMU (from RHEL.9.2)
Can reproduce this bug with qemu-kvm-7.2.0-14.el9_2.4.x86_64
Igor -
This bug is in a strange state - if ON_QA I'd expect there to be an ITR or FixVersion set or the TestOnly keyword being set. My concern / fear especially because of the Jira transition is that this will be lost. Can you elaborate a bit more or perhaps connect to https://issues.redhat.com/browse/RHEL-7173 (new Jira issue from the previous bug 2118240). Maybe we just need to migrate this bug manually (hint, use the "MigratedToJira" keyword - a bot will do the rest, then link that to the other Jira issue).