From: "Peter Huang(Peng)" <peter.huangpeng@huawei.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Question] why x2apic's set by default without host support(on Nehalem CPU).
Date: Mon, 22 Jul 2013 19:24:24 +0800 [thread overview]
Message-ID: <51ED1668.7030205@huawei.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Hi, Everyone
I have been encountered a problem recently.
My box uses Nehalem E5520 CPU, and this model doesn't support x2apic feature.
I created a VM on KVM, and uses cpu mode=pass-through, I can get the right cpu
model from the VM, but I can also see that the CPU in the vm supports x2apic.
This seems werid.
>From QEMU's CPU model definition, Nehalem also doesn't support x2apic.
Can anyone explain it?
Thanks to you all!
Below is the cpuinfo from host and guest:
host:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush
dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc
arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 sse4_2
popcnt lahf_lm dtherm tpr_shadow vnmi flexpriority ept vpid
vm:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush
mmx fxsr sse sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon rep_good
nopl pni ssse3 cx16 sse4_1 sse4_2 *x2apic *popcnt hypervisor lahf_lm
[-- Attachment #2: Type: text/html, Size: 3280 bytes --]
next reply other threads:[~2013-07-22 11:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 11:24 Peter Huang(Peng) [this message]
2013-07-22 12:36 ` [Qemu-devel] [Question] why x2apic's set by default without host support(on Nehalem CPU) Peter Huang(Peng)
2013-07-22 23:55 ` Marcelo Tosatti
2013-07-23 2:38 ` Peter Huang(Peng)
2013-07-22 13:41 ` Eduardo Habkost
2013-07-23 2:44 ` Peter Huang(Peng)
2013-07-23 11:27 ` Jiri Denemark
2013-07-24 0:48 ` Peter Huang(Peng)
2013-07-24 2:54 ` [Qemu-devel] [Solved]FYI//Re: " Peter Huang(Peng)
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=51ED1668.7030205@huawei.com \
--to=peter.huangpeng@huawei.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).