From: Liuyingdong <liuyingdong@huawei.com>
To: xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, wei.liu2@citrix.com,
andrew.cooper3@citrix.com,
"Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
dietmar.hahn@ts.fujitsu.com,
"huangzhichao@huawei.com >> Huangzhichao"
<huangzhichao@huawei.com>,
boris.ostrovsky@oracle.com
Subject: Question about XEN Hypervisor MSR capability exposion to VMs
Date: Sat, 31 Oct 2015 10:53:54 +0800 [thread overview]
Message-ID: <56342D42.1040304@huawei.com> (raw)
Hi All
We encountered a blue screen problem when live migrate
Win8.1/Win2012R2 64bit VM from V3 processor to non-V3
processor sandbox, KVM does not has this problem.
After looking into the MSR capabilities, we found XEN
hypervisor exposed bit 39 and bit 18 to the VM, from
Intel manual bit 39 refers to reserve bit and should
not be set, bit 18 refers to MWAIT/MONITOR capability,
from my understanding it should not exposed to the VM
too.
BTW, KVM does not expose bit 18/39 to the VM.
Below is the boot message:
(XEN) read msr: ecx=c0000083, msr_value=0xfffff80028ddf240
(XEN) read msr: ecx=1a0, msr_value=0x4000801889
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(XEN) write msr:msr=40000071, msr_value=0x10000000000082f
(XEN) write msr:msr=40000070, msr_value=0x0
(XEN) write msr:msr=40000071, msr_value=0x20000000000082f
(XEN) write msr:msr=40000070, msr_value=0x0
(XEN) read msr: ecx=17, msr_value=0x0
(XEN) write msr:msr=8b, msr_value=0x0
(XEN) read msr: ecx=8b, msr_value=0x2d00000000
next reply other threads:[~2015-10-31 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 2:53 Liuyingdong [this message]
2015-11-02 2:04 ` Question about XEN Hypervisor MSR capability exposion to VMs Zhang, Yang Z
2015-11-02 11:00 ` Andrew Cooper
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=56342D42.1040304@huawei.com \
--to=liuyingdong@huawei.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dietmar.hahn@ts.fujitsu.com \
--cc=huangzhichao@huawei.com \
--cc=kevin.tian@intel.com \
--cc=peter.huangpeng@huawei.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.