Bug 817250
Summary: | [KVM] can't install or boot up 32bit Win8(Beta) guest | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Yongjie Ren <yongjie.ren> |
Component: | qemu-kvm | Assignee: | Yvugenfi <yvugenfi> |
Status: | CLOSED DUPLICATE | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | acathrow, areis, bcao, bsarathy, chao.zhou, chrisw, ddugger, ddutile, dyasny, gabrielx.wu, gleb, haitao.shan, juzhang, michen, mkenneth, rpacheco, shuang, tburke, virt-maint, xiantao.zhang |
Target Milestone: | beta | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-01 06:52:12 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Yongjie Ren
2012-04-28 09:48:17 UTC
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. 0x0000005D is "unsupported processor" error code. What exact command line virt-manager is using to start the VM? (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. Will be fixed when the decision to support Windows 8 will be taken. *** Bug 832301 has been marked as a duplicate of this bug. *** 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. re-open bug 832301 to trace this issue. 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 *** |