[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: "Andrew Cooper" <andrew.cooper3@xxxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Fri, 14 Oct 2016 00:39:23 -0600
Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Fri, 14 Oct 2016 06:39:29 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> 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.

Jan

_______________________________________________
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: Andrew Cooper

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

Prev by Date: Re: [Xen-devel] [PATCH 0/3 for 4.8] docs: feature documents for the schedulers
Next by Date: Re: [Xen-devel] [RFC KERNEL PATCH 0/2] Add Dom0 NVDIMM support for Xen
Previous by thread: Re: [Xen-devel] [PATCH v2 2/2] x86/vmx: Reduce the verbosity of the vmentry failure error reporting
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®.