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.

Created attachment 504057 [details]
guest domain config

Description of problem:
On an Intel host with 96 CPUs and 1T mem, RHEL 6.1 Xen HVM fails to boot. It crashes a few seconds after it's created, endlessly outputing some like "BUG: soft lockup - CPU#1 stuck for 106s!".

Tested 64 bit and 32 bit guests, both crashed.

Version-Release number of selected component (if applicable):
guest: kernel-2.6.32-131.0.15.el6
host: kernel-xen-2.6.18-267.el5, xen-3.0.3-132.el5
CPU is Intel Xeon E7450, with 1T memory.

How reproducible:
Always

Steps to Reproduce:
1.
On the described host, xm create the HVM domain using the attached config.
2.
3.
  
Actual results:
Guest crash after a while.

Expected results:
Don't crash.

Additional info:
RHEL 6 PV guest does not crash in the same env.

Created attachment 504058 [details]
guest console output

Created attachment 504059 [details]
xend log

Created attachment 504060 [details]
xm dmesg

Oh, I forgot one thing: the HVM guest is given more than 1 vcpus. Single vcpu did not trigger the crash.

Try clocksource=jiffies on the guest kernel command line.

(In reply to comment #8)
> Try clocksource=jiffies on the guest kernel command line.

That's working!

It doesn't crash after adding clocksource=jiffies.

*** This bug has been marked as a duplicate of bug 661211 ***