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.
+++ This bug was initially created as a clone of Bug #524052 +++
Description of problem:
Attempted to boot a fully virtualized DomU with rawhide's 2.6.31-14.fc12.x86_64 for installation hangs almost immediately.
How reproducible:
100%
Steps to Reproduce:
virt-install \
--hvm \
--name=rawhide \
--ram=2048 \
--file=/vm/rawhide.img \
--file-size=8 \
--location=/mnt/download/fedora/linux/development/x86_64/os
Select install from the boot menu
Actual results:
Hangs after printing the following
Loading vmlinuz............
Loading initrd.img................
Probing EDD (edd=off to disable)... ok
Expected results:
boots
Additional info:
There are no logs in xm dmesg
Note, a 32-bit HVM boots and installs on a 32-bit host
--- Additional comment from drjones on 2009-09-17 13:36:35 EDT ---
Moving to kernel-xen for now since a 64-bit HVM rawhide boots past this point on an upstream Xen host.
Comment 2RHEL Program Management
2009-09-17 18:27:40 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Ok, I've bisected this down on the upstream kernel to a patch that enables xsave,
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=dc1e35c6e95e8923cf1d3510438b63c600fee1e2
Overriding that capability as "not supported" allows the HVM guest to boot.
I'm looking at how to deal with it now. There's been some discussion of it in upstream Xen, but nothing too conclusive as far as I can tell.
Masking this capability from the guest might be the best option.
This bug will probably be closed as not a bug, since the problem is best solved in the hypervisor, see bug 524052. Regarding the 32-bit HVM booting that was stated in comment 1. That was reported from a different machine, probably one not supporting xsave. On my machine 32-on-32 fails the same way as with 64b.
Also note: if you need to boot f12/RHEL6 on a hypervisor that doesn't mask XSAVE you can still do it by adding noxsave to the kernel command line.
Installing a RHEL6 guest on a RHEL5.4 hypervisor will most likely fail on relatively recent hardware. This is because RHEL5.4 does not hide new hardware features that are supported by the 2.6.32 kernel but not by the hypervisor. RHEL5.5 fixed this.
Should we require release notes for this, or should we just close it as NOTABUG?
Well it is correct to close this as not a bug as it is not a RHEL 6 issue. But the question remains if we should be z-streaming the RHEL 5.5 fix for 5.4.z
and RHEV too.