xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"publicity@lists.xenproject.org" <publicity@lists.xenproject.org>,
	"'Jan Beulich (JBeulich@suse.com)'" <JBeulich@suse.com>,
	"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>
Subject: Re: Xen nested wiki
Date: Fri, 14 Feb 2014 15:40:41 +0100	[thread overview]
Message-ID: <1392388841.32038.263.camel@Solace> (raw)
In-Reply-To: <52FDEEDB.40305@eu.citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1809 bytes --]

On ven, 2014-02-14 at 10:24 +0000, George Dunlap wrote:
> On 02/14/2014 01:13 AM, Zhang, Yang Z wrote:

> > Sorry. I didn't clarify it clearly. Most of the patches to run nested are already in Xen upstream. What I want is to add "nested is basically supported in Xen 4.4" in the Xen 4.4 release note to let people know it.
> 
> I'm afraid "basically supported" will imply to people that they might 
> consider shipping it on production systems.  But because of the issues 
> with shadow-on-HAP, and the potential locking issues with the nested p2m 
> table, both of which are in control of the guest admin rather than the 
> host admin, I don't think that's a recommendation we can make at this time.
> 
> But I do think making some kind of announcement about common 
> functionality being complete and ready to be tested would be a good 
> idea.  When we come to make the release we can brainstorm on what 
> wording to use.
> 
I agree. Let's not sell something not entirely ready, as that could
backfire, but we should at least hint that it's there and it's improved.

> Actually, I wonder whether advertising Win7's XP compatibility mode as a 
> separate "tech preview" feature would make sense.  The people who use 
> that feature are very likely very different than most other people who 
> might think about using nested virtualization.
> 
Completely agree again. And this is something that could be very well
described in a blog post on the subject (happening after the release), I
think. :-)

Regads,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2014-02-14 14:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  3:55 Xen nested wiki Zhang, Yang Z
2014-02-13 10:29 ` Dario Faggioli
2014-02-14  1:13   ` Zhang, Yang Z
2014-02-14 10:24     ` George Dunlap
2014-02-14 14:40       ` Dario Faggioli [this message]
2014-02-17  1:16         ` Zhang, Yang Z
2014-02-14 14:36     ` Dario Faggioli
2014-02-13 10:36 ` Pasi Kärkkäinen
2014-02-14  1:20   ` 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=1392388841.32038.263.camel@Solace \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=publicity@lists.xenproject.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 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).