Bug 60782 - [Nested] Windows XP Mode can not work
Summary: [Nested] Windows XP Mode can not work
Status: NEW
Alias: None
Product: Virtualization
Classification: Unclassified
Component: kvm (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: virtualization_kvm
URL:
Keywords:
Depends on:
Blocks: 94971
  Show dependency tree
 
Reported: 2013-08-23 03:39 UTC by Zhou, Chao
Modified: 2016-02-16 21:47 UTC (History)
4 users (show)

See Also:
Kernel Version: 3.11.0-rc1
Subsystem:
Regression: No
Bisected commit-id:

Attachments
error message (31.39 KB, image/jpeg)
2013-08-23 03:39 UTC, Zhou, Chao 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Zhou, Chao 2013-08-23 03:39:43 UTC 
Created attachment 107286 [details]
error message

Environment:
------------
Host OS (ia32/ia32e/IA64):ia32e
Guest OS (ia32/ia32e/IA64):ia32e
Guest OS Type (Linux/Windows):Windows7
kvm.git Commit:205befd9a5c701b56f569434045821f413f08f6d
qemu-kvm Commit:7477cd3897082d2650d520a4e9aa7f8affa3dd5d
Host Kernel Version:3.11.0-rc1


Bug detailed description:
--------------------------
Boot up win7 guest with -cpu host, then launch XP-Mode. You can found it from http://www.microsoft.com/en-us/download/details.aspx?id=8002. Error message pops out and shows 'hardware-assisted virtualization is disabled', but use "GenuineCheck" or other tools from Microsoft to checked, they both
show hardware-assisted virtualization is supported.

note: 
xp mode version:1.3.7600.16422
virutual pc version :6.1.7600.16393


Reproduce steps:
----------------
1. qemu-system-x86_64 -enable-kvm -m 4G -smp 2 -net
nic,macaddr=00:12:34:12:42:14 -net tap,script=/etc/kvm/qemu-ifup
win7xpmode.qcow -cpu host  
2.install xpmode
3.launch xpmode

Current result:
----------------
error message pops out


Expected result:
----------------
xpmode boot up successfully.
Comment 1 Paolo Bonzini 2013-08-23 10:02:46 UTC 
Try "-cpu host,+vmx" instead.
Comment 2 Zhou, Chao 2013-08-26 02:12:27 UTC 
(In reply to Paolo Bonzini from comment #1)
> Try "-cpu host,+vmx" instead.

This issue still exists.
Note You need to log in before you can comment on or make changes to this bug.