All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Jeroen Groenewegen van der Weyden <groen692@grosc.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>
Subject: Re: Crash of guest with nested vmx with Unknown nested vmexit reason 80000021.
Date: Fri, 27 Feb 2015 08:08:13 +0000	[thread overview]
Message-ID: <54F033FD02000078000646CA@mail.emea.novell.com> (raw)
In-Reply-To: <54EF6C7B.3040206@grosc.com>

>>> On 26.02.15 at 19:56, <groen692@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, <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
>>
>>

  reply	other threads:[~2015-02-27  8:08 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
2014-12-09  9:17                   ` Jan Beulich
2015-02-26 18:56                     ` Jeroen Groenewegen van der Weyden
2015-02-27  8:08                       ` Jan Beulich [this message]
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=54F033FD02000078000646CA@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=groen692@grosc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.