All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>,
	"Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: Status of Nested Virt in 4.4 (Was: Re: Xen 4.4 development update)
Date: Fri, 24 Jan 2014 14:47:11 +0000	[thread overview]
Message-ID: <52E27CEF.2010009@eu.citrix.com> (raw)
In-Reply-To: <1389951634.6697.43.camel@kazak.uk.xensource.com>

On 01/17/2014 09:40 AM, Ian Campbell wrote:
> On Fri, 2014-01-17 at 02:16 +0000, Zhang, Yang Z wrote:
>> As Andrew said, nested still in experimental stage, because there are
>> still lots of scenarios I am not covered in my testing. So it may not
>> accurate to say it is good supported. But I hope people know that the
>> nested is ready to use now. And encourage them to try it and report
>> bug to us to push nested move forward.
> Perhaps we could say it is "tech preview" rather than "experimental"?

If { {xp,win7,win8,rhel6}x{x86,x64} } x { Xen, KVM, VMWare } and Win7 XP 
compatibility mode are tested regularly, and only HyperV, L2 shadow, and 
paging / PoD don't work, I think we should be able to call this a "1.0" 
release for nested virt.  Then we can add in "now works with HyperV", 
"Now works with shadow", "Now works with paging" as those become mature.

I think if we have a wiki page describing what is expected to work, and 
some of the key things that don't work, then we should be able to add 
"Basic nested virt support for VMX no longer experimental (see the the 
wiki for details)" to the "4.4 feature" list.

  -George

  parent reply	other threads:[~2014-01-24 14:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 13:16 Xen 4.4 development update Ian Campbell
2014-01-08 13:19 ` qemu-upstream not freeing pirq (Was: Re: Xen 4.4 development update) Ian Campbell
2014-01-08 13:22   ` Stefano Stabellini
2014-01-08 13:55     ` Pasi Kärkkäinen
2014-01-08 14:23       ` Konrad Rzeszutek Wilk
2014-01-08 13:19 ` Race in PV shutdown between tool detection and shutdown watch " Ian Campbell
2014-01-08 13:22   ` David Vrabel
2014-01-08 14:24     ` Konrad Rzeszutek Wilk
2014-01-08 13:29 ` Xen 4.4 development update Ian Campbell
2014-01-08 13:30   ` Ian Campbell
2014-01-08 14:21 ` Sander Eikelenboom
2014-01-08 14:23   ` Ian Campbell
2014-01-08 14:35 ` Wei Liu
2014-01-16  6:54 ` Zhang, Yang Z
2014-01-16  9:45   ` Status of Nested Virt in 4.4 (Was: Re: Xen 4.4 development update) Ian Campbell
2014-01-16 10:03     ` Andrew Cooper
2014-01-16 10:03     ` Jan Beulich
2014-01-17  2:16       ` Zhang, Yang Z
2014-01-17  9:40         ` Ian Campbell
2014-01-24  7:59           ` Zhang, Yang Z
2014-01-24  8:22             ` Ian Campbell
2014-01-24 14:47           ` George Dunlap [this message]
2014-01-24 14:56             ` Tim Deegan
2014-01-24 15:02               ` Ian Campbell
2014-01-24 16:04                 ` George Dunlap
2014-01-26  8:45                   ` 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=52E27CEF.2010009@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.