Comment 4 for bug 921208

Revision history for this message
Alexandre Derumier (aderumier-odiso) wrote :

I could you try with "-cpu host,level=2"

I see you have a westmere cpu, and maybe this is related:

I'm developper on the proxmox distribution.

We are using kvm git, and one of our user can't boot guest win7x64
with -cpu host. (but it's working with linux guest).

It's working fine with -cpu host,level=9

but not with -cpu host,level=10 or level=11.

We also try with new Westermere cpudefs in target-x86_64.conf
(see redhat patches from february 2012)

[cpudef]
   name = "Westmere"
   level = "11"
   vendor = "GenuineIntel"
   family = "6"
   model = "44"
   stepping = "1"
   feature_edx = "sse2 sse fxsr mmx clflush pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc pse de fpu"
   feature_ecx = "aes popcnt sse4.2 sse4.1 cx16 ssse3 sse3"
   extfeature_edx = "i64 syscall xd"
   extfeature_ecx = "lahf_lm"
   xlevel = "0x8000000A"
   model_id = "Westmere E56xx/L56xx/X56xx (Nehalem-C)"

That also doesn't without change level < 10.

User also report that "-cpu host" was working fine with qemu 0.15.

I see that other intel cpudefs in target-x86_64.conf have level=2, maybe does it need to be the same for westmere ?

Best Regards,

Alexandre Derumier