From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Crash of guest with nested vmx with Unknown nested vmexit reason 80000021. Date: Fri, 27 Feb 2015 08:08:13 +0000 Message-ID: <54F033FD02000078000646CA@mail.emea.novell.com> References: <542AD266.5030803@grosc.com> <5433B94E020000780003CBF0@mail.emea.novell.com> <5437B593.80702@grosc.com> <543F84CD020000780003F02A@mail.emea.novell.com> <5450F6E2.6050807@grosc.com> <545127160200007800043328@mail.emea.novell.com> <5486BC53.2080608@grosc.com> <5486CC51020000780004E01A@mail.emea.novell.com> <54EF6C7B.3040206@grosc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54EF6C7B.3040206@grosc.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jeroen Groenewegen van der Weyden Cc: Kevin Tian , George Dunlap , Eddie Dong , "xen-devel@lists.xen.org" , Jun Nakajima , Yang Z Zhang List-Id: xen-devel@lists.xenproject.org >>> On 26.02.15 at 19:56, wrote: > Anything planned concerning this? Thanks for asking, but to be honest I don't understand why you're (not the first time iirc) pinging me rather than the VMX maintainers who had promised to do that work. All I can say is that I'm being told it's still on their todo list, but no-one has found time yet. And please remember that all of nested virt is still marked preview, i.e. not fully supported - for reasons like the bug here. Jan > Jan Beulich schreef op 9-12-2014 om 10:17: >>>>> On 09.12.14 at 10:09, 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 >> >>