qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Westmere cpu : guest win7 x64 doesn't boot with -cpu host (cpu level problem)
Date: Thu, 23 Feb 2012 07:26:55 +0100 (CET)	[thread overview]
Message-ID: <4fd08647-02d4-4dfd-843f-34d92af2a5ff@mailpro> (raw)

Hi,
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

             reply	other threads:[~2012-02-23  6:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23  6:26 Alexandre DERUMIER [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-02-23  6:26 [Qemu-devel] Westmere cpu : guest win7 x64 doesn't boot with -cpu host (cpu level problem) Alexandre DERUMIER

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4fd08647-02d4-4dfd-843f-34d92af2a5ff@mailpro \
    --to=aderumier@odiso.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).