Can’t install or boot up 32bit win8 guest.

Bug #1007269 reported by Yongjie Ren
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
QEMU
Confirmed
Undecided
Unassigned

Bug Description

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Linux(rhel6u1)
kvm.git Commit:51bfd2998113e1f8ce8dcf853407b76a04b5f2a0
qemu-kvm Commit:3fd9fedb9fae4517d93d76e93a2924559cacf2f6
Host Kernel Version:3.4.0-rc7
Hardware:WSM-EP,Romley-EP

Bug detailed description:
--------------------------
it can't install or boot up 32bit Win8(Consumer Preview Update 2) guest. The guest will crash with the following error, while 64bit Win8 and 32bit Win7 guest work fine.
-----Win8 Error-------
Your computer needs to restart.
Please hold down the power button.
Error code: 0x0000005D
Parameters:
0x03060D03
0x756E6547
0x49656E69
0x6C65746E
-----Win8 Error-------

"0x0000005D" code means "UNSUPPORTED_PROCESSOR" in Windows.

BTW, you can get 32bit Win8 ISO from the following website.
http://windows.microsoft.com/en-US/windows-8/iso

Reproduce steps:
----------------
1. get 32 bit win8 ISO
2. prepare a disk image: dd if=/dev/zero of=/root/win8-32.img bs=1M count=16384
3. start a guest to install 32bit win8: qemu-system –m 4096 –smp 4 –hda /root/win8-32.img –cdrom /media/32bit-Win8.iso
4. if you have a 32bit win8 image,try to boot it up

Current result:
----------------
32bit Win8 guest crash

Expected result:
----------------
32bit win8 guest boot up correctly

Revision history for this message
Rovano (rovano) wrote :

I use Virtualbox latest and same problem.
Try 64 edition Windows...

Revision history for this message
Rovano (rovano) wrote :

Vmware player 4.0.2 is ok.

Revision history for this message
Yongjie Ren (yongjie-ren) wrote :

64bit Win8 client can work fine as a kvm guest, however, 32bit can't work.

Revision history for this message
Jan Kiszka (jan-kiszka) wrote :

Try varying the CPU type (-cpu ...). Some work for me here, others don't. Likely some subtle bug(s) in the definitions.

Revision history for this message
Yongjie Ren (yongjie-ren) wrote :

For 32bit Win8, I used different cpu mode and got different results as following.
n270: can boot up
athlon: fail (Error code: 0x0000005D)
pentium3: can boot up
pentium2: fail(Error code: 0x0000005D)
Pentium: fail(error code: 0xc0000260)
486: fail(error code: 0xc0000260)
Coreduo: can boog up
Kvm32: can boot up
Qemu32: can boot up
Kvm64: can bootup
Core2duo: can boot up
Phenom: can boot up
Qemu64: fail (Error code: 0x0000005D)

[root@jay-linux ~]# qemu-system-x86_64 -cpu ?
x86 [n270]
x86 [athlon]
x86 [pentium3]
x86 [pentium2]
x86 [pentium]
x86 [486]
x86 [coreduo]
x86 [kvm32]
x86 [qemu32]
x86 [kvm64]
x86 [core2duo]
x86 [phenom]
x86 [qemu64]

Revision history for this message
Marcelo Tosatti (mtosatti) wrote :

PAE/NX/SSE2 Support Requirement Guide for Windows 8

http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/error-when-installing-windows-8-release-preview/a2c11f2c-d43b-44fc-9bc0-61805a2d95ef

Perhaps adding 3DNow allows qemu64 to boot?

In any case, this is not a KVM bug.

Revision history for this message
Yongjie Ren (yongjie-ren) wrote :

qemu64 cpu model has PAE/NX/SSE2 Support by default.
Also, after I used "-cpu qemu64,+3dnow", 32bit Win8 also can't be installed and had a BSOD with "Error code: 0x0000005D".

Revision history for this message
chao zhou (chao-zhou) wrote :

It's not a KVM bug.

Changed in qemu:
status: New → Invalid
Revision history for this message
Stefan Weil (ubuntu-weilnetz) wrote :

It's not a KVM bug, but a well known problem of QEMU without KVM (TCG). There is currently no solution.

Changed in qemu:
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.