Hi All,
I found a way to preproduce the bug very easy by using the
apic-send_IPI_all(NMI_VECTOR)
in L2 in a kernel module to trigger MNI. And I have verified that the bug can
be fixed as Jan's
suggestion, ' the second half of vmx_idtv_reinject() needs to be done without
regard to
nestedhvm_vcpu_in_guestmode(v)', I will send a patch later.
Liang
-Original Message-
From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
boun...@lists.xen.org] On Behalf Of Jeroen Groenewegen van der Weyden
Sent: Wednesday, March 04, 2015 6:24 PM
To: Jan Beulich
Cc: Tian, Kevin; George Dunlap; Dong, Eddie; xen-devel@lists.xen.org;
Nakajima, Jun; Zhang, Yang Z
Subject: Re: [Xen-devel] Crash of guest with nested vmx with Unknown
nested vmexit reason 8021.
Hi Jan,
I am sorry, But had the impression you were somehow the owner of these
feature. My mistake.
I understand the feature is in preview, But are you feeling intense presure
when I ask for some status every 2 months? :-))
BR,
Jeroen
Jan Beulich schreef op 27-2-2015 om 09:08:
On 26.02.15 at 19:56, groen...@grosc.com 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, groen...@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
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
