[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 1/2] x86/vmx: Print the problematic MSR if a vmentry fails

To: Jan Beulich <JBeulich@xxxxxxxx>
From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
Date: Fri, 14 Oct 2016 10:29:22 +0100
Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Fri, 14 Oct 2016 09:29:42 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 14/10/16 07:39, Jan Beulich wrote:
>>>> On 13.10.16 at 15:46, <andrew.cooper3@xxxxxxxxxx> wrote:
>> Sample error looks like:
>>
>>   (XEN) Failed vm entry (exit reason 0x80000022) caused by MSR loading 
>> (entry 13).
>>   (XEN)   msr 0000068a, val 1fff800000102af0, (mbz 0)
> A _really_ minor remark: This is no longer in line with what gets
> actually logged.

Oops yes.  Fixed locally.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] [PATCH v2 1/2] x86/vmx: Print the problematic MSR if a vmentry fails
  - From: Tian, Kevin

References:
- [Xen-devel] [PATCH 1/2] x86/vmx: Print the problematic MSR if a vmentry fails
  - From: Andrew Cooper
- [Xen-devel] [PATCH v2 1/2] x86/vmx: Print the problematic MSR if a vmentry fails
  - From: Andrew Cooper
- Re: [Xen-devel] [PATCH v2 1/2] x86/vmx: Print the problematic MSR if a vmentry fails
  - From: Jan Beulich

Prev by Date: Re: [Xen-devel] [PATCH 0/3 for 4.8] docs: feature documents for the schedulers
Next by Date: [Xen-devel] [PATCH] x86emul: fix pushing of selector registers
Previous by thread: Re: [Xen-devel] [PATCH v2 1/2] x86/vmx: Print the problematic MSR if a vmentry fails
Next by thread: Re: [Xen-devel] [PATCH v2 1/2] x86/vmx: Print the problematic MSR if a vmentry fails
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.