From: "Peter Huang(Peng)" <peter.huangpeng@huawei.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Question] why x2apic's set by default without host support(on Nehalem CPU).
Date: Tue, 23 Jul 2013 10:44:48 +0800 [thread overview]
Message-ID: <51EDEE20.4060206@huawei.com> (raw)
In-Reply-To: <20130722134138.GE19826@otherpad.lan.raisama.net>
> libvirt's "host-passthrough" uses "-cpu host', and it "-cpu host"
> enables every feature that can be enabled on the host.
>From my test results, I found that even when use host-passthrough mode, VM's
cpu features are very different from host, this doesn't match what host-passthrough
mode's explanation.
libvirt's option exlanation:
With this mode, the CPU visible to the guest should be exactly the same as the host
CPU even in the aspects that libvirt does not understand.
> If the behavior of "-cpu host" doesn't match libvirt expectations, we
> need to clarify what are the requirements, and maybe have a "try to be
> close to host CPU mode" as opposed to the current "enable everything
> that can be enabled" mode.
Does the results above indicates what you mean to do? or the current way doesn't work
as we expect.
Thanks!
next prev parent reply other threads:[~2013-07-23 2:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 11:24 [Qemu-devel] [Question] why x2apic's set by default without host support(on Nehalem CPU) Peter Huang(Peng)
2013-07-22 12:36 ` 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) [this message]
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=51EDEE20.4060206@huawei.com \
--to=peter.huangpeng@huawei.com \
--cc=ehabkost@redhat.com \
--cc=libvir-list@redhat.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).