From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeroen Groenewegen van der Weyden <groen692@grosc.com>
Subject: Re: Crash of guest with nested vmx with Unknown nested
 vmexit reason 80000021.
Date: Thu, 26 Feb 2015 19:56:59 +0100
Message-ID: <54EF6C7B.3040206@grosc.com>
References: <542AD266.5030803@grosc.com>
	<5433B94E020000780003CBF0@mail.emea.novell.com>
	<AADFC41AFE54684AB9EE6CBC0274A5D1260A4A7B@SHSMSX101.ccr.corp.intel.com>
	<5437B593.80702@grosc.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0ABAF528@SHSMSX104.ccr.corp.intel.com>
	<543F84CD020000780003F02A@mail.emea.novell.com>
	<5450F6E2.6050807@grosc.com>
	<545127160200007800043328@mail.emea.novell.com>
	<CAFLBxZZ5itYWTDsnkGHzy0_4SWU6QMXnVpkYAFMOH+wG+5MKJQ@mail.gmail.com>
	<5486BC53.2080608@grosc.com>
	<5486CC51020000780004E01A@mail.emea.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <5486CC51020000780004E01A@mail.emea.novell.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: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>, George Dunlap <George.Dunlap@eu.citrix.com>, Eddie Dong <eddie.dong@intel.com>, "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>, Jun Nakajima <jun.nakajima@intel.com>, Yang Z Zhang <yang.z.zhang@intel.com>
List-Id: xen-devel@lists.xenproject.org

Hi Jan,

Anything planned concerning this?

BR,
Jeroen.

Jan Beulich schreef op 9-12-2014 om 10:17:
>>>> On 09.12.14 at 10:09, <groen692@grosc.com> 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
>
>