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:
In RHEL6.3, it can't install or boot up 32bit Win8(beta) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine. And, 32bit Win8 guest works fine in RHEL6.2 GA.
-----Win8 Error-------
Your computer needs to restart.
Please hold down the power button.
Error code: 0x0000005D
Parameters:
0x03060D03
0x756E6547
0x49656E69
0x6C65746E
-----Win8 Error-------
BTW, you can get 32bit Win8 ISO from the following website.
http://windows.microsoft.com/en-US/windows-8/iso
Version-Release number of selected component (if applicable):
RHEL6.3 virtualization RPM packages:
qemu-kvm-0.12.1.2-2.272.el6.x86_64
kernel-2.6.32-262.el6.x86_64
libvirt-0.9.10-11.el6.x86_64
virt-manager-0.9.0-11.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1.get 32bit Win8 ISO
2.try to install 32bit Win8 guest in virt-manager
3.(if you already have a 32bit Win8 image, try to boot it up.)
Actual results:
32bit Win8 guest crash
Expected results:
install and boot up correctly
Additional info:
Since win8 is not yet a fully supported release I'm moving the bug into the next minor release. We'll look into it anyway to look for the hypervisor issue.
(In reply to comment #3)
> 0x0000005D is "unsupported processor" error code. What exact command line
> virt-manager is using to start the VM?
Yeah, it means "unsupported processor".
We can reproduce it in a very simple qemu-kvm command line as following.
/usr/libexec/qemu-kvm -m 1024 -hda win8_32.img
The same command line can start the 32bit Win8 guest in RHEL6.2 GA.
Comment 5Yvugenfi@redhat.com
2012-06-05 11:25:10 UTC
Will be fixed when the decision to support Windows 8 will be taken.
Now windows 8 RP(Release Preview) version is born out ,and HCK has already provide the system test and driver test for win8 .
I suggest to to fix this bug in rhel6.4 .Correct me if I were wrong
Thanks,
Mike
(In reply to comment #7)
> Now windows 8 RP(Release Preview) version is born out ,and HCK has already
> provide the system test and driver test for win8 .
>
> I suggest to to fix this bug in rhel6.4 .Correct me if I were wrong
>
Agree, win8 install should be part of the acceptance criteria of RHEL6.4.
(In reply to comment #4)
> (In reply to comment #3)
> > 0x0000005D is "unsupported processor" error code. What exact command line
> > virt-manager is using to start the VM?
> Yeah, it means "unsupported processor".
> We can reproduce it in a very simple qemu-kvm command line as following.
> /usr/libexec/qemu-kvm -m 1024 -hda win8_32.img
>
> The same command line can start the 32bit Win8 guest in RHEL6.2 GA.
As Gleb said, without specifying a virtual cpu model you're using qemu's default which is just a fake cpu. Please use one of the supported virtual model for Intel or AMD (you can query qemu top the supported list by running qemu -cpu ?).
I'll close the bug as we do have reports it works.
OK. Please have a look at the following bug (about the same issue).
https://bugs.launchpad.net/qemu/+bug/1007269
Some CPU models(e.g. Qemu32, Core2duo) can work for 32bit Win8. Some(e.g. qemu64) can't work.
(In reply to comment #11)
> OK. Please have a look at the following bug (about the same issue).
> https://bugs.launchpad.net/qemu/+bug/1007269
>
> Some CPU models(e.g. Qemu32, Core2duo) can work for 32bit Win8. Some(e.g.
> qemu64) can't work.
qemu32 and qemu64 are not the right models, but we have another report from QA and I'll check them up and may re-open the bug. Thanks for the response.
Actually Bug 832301 and this one are the same bugs . I tried all the supported cpu type ,none of them works ,Since Bug 832301 was been reopened ,let's use that one to track this bug .
*** This bug has been marked as a duplicate of bug 832301 ***