From: Jeroen Groenewegen van der Weyden <groen692@grosc.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Yang Z Zhang <yang.z.zhang@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Eddie Dong <eddie.dong@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Crash of guest with nested vmx with Unknown nested vmexit reason 80000021.
Date: Tue, 09 Dec 2014 10:09:39 +0100 [thread overview]
Message-ID: <5486BC53.2080608@grosc.com> (raw)
In-Reply-To: <CAFLBxZZ5itYWTDsnkGHzy0_4SWU6QMXnVpkYAFMOH+wG+5MKJQ@mail.gmail.com>
Hi All,
Did anyone find the time yet? I'm still more then willing testing any
patches.
BR,
Jeroen.
George Dunlap schreef op 3-11-2014 om 12:16:
> I think what Jan means is, sorry, we haven't had a chance to actually
> work on this yet, but thanks for the ping.:-)
>
> -George
next prev parent reply other threads:[~2014-12-09 9:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 15:55 Crash of guest with nested vmx with Unknown nested vmexit reason 80000021 Jeroen Groenewegen van der Weyden
2014-10-01 13:20 ` Jan Beulich
2014-10-07 7:58 ` Jan Beulich
2014-10-07 15:16 ` Jeroen Groenewegen van der Weyden
2014-10-07 19:56 ` Tian, Kevin
2014-10-10 10:31 ` Jeroen Groenewegen van der Weyden
2014-10-16 6:18 ` Zhang, Yang Z
2014-10-16 6:41 ` Jan Beulich
2014-10-29 14:17 ` Jeroen Groenewegen van der Weyden
2014-10-29 16:42 ` Jan Beulich
2014-11-03 11:16 ` George Dunlap
2014-12-09 9:09 ` Jeroen Groenewegen van der Weyden [this message]
2014-12-09 9:17 ` Jan Beulich
2015-02-26 18:56 ` Jeroen Groenewegen van der Weyden
2015-02-27 8:08 ` Jan Beulich
2015-03-04 10:24 ` Jeroen Groenewegen van der Weyden
2015-04-07 7:18 ` Li, Liang Z
2014-10-16 6:27 ` Zhang, Yang Z
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5486BC53.2080608@grosc.com \
--to=groen692@grosc.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=eddie.dong@intel.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).