From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Question about XEN Hypervisor MSR capability
	exposion to VMs
Date: Mon, 2 Nov 2015 11:00:13 +0000
Message-ID: <5637423D.5070000@citrix.com>
References: <56342D42.1040304@huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <56342D42.1040304@huawei.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Liuyingdong <liuyingdong@huawei.com>, xen-devel@lists.xen.org
Cc: kevin.tian@intel.com, wei.liu2@citrix.com, "Huangpeng
	(Peter)" <peter.huangpeng@huawei.com>, dietmar.hahn@ts.fujitsu.com, "huangzhichao@huawei.com >>
	Huangzhichao" <huangzhichao@huawei.com>, boris.ostrovsky@oracle.com
List-Id: xen-devel@lists.xenproject.org

On 31/10/15 02:53, Liuyingdong wrote:
> 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
>

Xen currently does not make any attempt to level MSRs (it is unfortunate
that this area has been overlooked).

I have also encountered windows BSODs for this - 0x109 Critical
Structure Corruption I am guessing?

I am currently working on fixes to CPUID levelling (as it is more
important than MSRs at the moment), but have plans to fix MSR levelling
after that.

~Andrew