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

Re: [Xen-devel] Crash of guest with nested vmx with Unknown nested vmexit reason 80000021.

To: "Jeroen Groenewegen van der Weyden" <groen692@xxxxxxxxx>
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Tue, 09 Dec 2014 09:17:53 +0000
Cc: Kevin Tian <kevin.tian@xxxxxxxxx>, George Dunlap <George.Dunlap@xxxxxxxxxxxxx>, Eddie Dong <eddie.dong@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>, Jun Nakajima <jun.nakajima@xxxxxxxxx>, Yang Z Zhang <yang.z.zhang@xxxxxxxxx>
Delivery-date: Tue, 09 Dec 2014 09:18:28 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

>>> On 09.12.14 at 10:09, <groen692@xxxxxxxxx> wrote:
> Did anyone find the time yet? I'm still more then willing testing any 
> patches.

Just yesterday we were told by Intel that they still can't foresee when
they will find time.

Jan


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

References:
- Re: [Xen-devel] Crash of guest with nested vmx with Unknown nested vmexit reason 80000021.
  - From: Jeroen Groenewegen van der Weyden

Prev by Date: Re: [Xen-devel] [PATCH v2] console: increase initial conring size
Next by Date: Re: [Xen-devel] [v8][PATCH 04/17] update the existing hypercall to support XEN_DOMCTL_set_rdm
Previous by thread: Re: [Xen-devel] Crash of guest with nested vmx with Unknown nested vmexit reason 80000021.
Index(es):
- Date
- Thread

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