From: George Dunlap <george.dunlap@eu.citrix.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>,
Russell Pavlicek <russell.pavlicek@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Please review the key 4.4 release docs
Date: Fri, 14 Mar 2014 17:24:41 +0000 [thread overview]
Message-ID: <53233B59.8080208@eu.citrix.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AA11B08@SHSMSX104.ccr.corp.intel.com>
On 03/11/2014 01:23 AM, Zhang, Yang Z wrote:
> George Dunlap wrote on 2014-03-10:
>> On 03/10/2014 04:27 AM, Zhang, Yang Z wrote:
>>> Russell Pavlicek wrote on 2014-03-10:
>>>> I have done my best to compile the various key release documents
>>>> for the 4.4 release.
>>>>
>>>> All have hyperlinks from the download page:
>>>> http://www.xenproject.org/downloads/xen-archives/supported-xen-44-s
>>>> er
>>>> i
>>>> es/ xen-440.html
>>> I thought that we have agreed that we will move the nested
>>> virtualization
>> from experimental to 1.0 or something else in Xen 4.4 release note.
>> But it seems it still in experimental state and there is no mention of
>> it in the release note.
>>
>> Well we discussed it, but there were too many things still missing to
>> call it a properly supported feature: in particular, doubts about how
>> well shadow-on-hap would work, which would be a potential security
> Actually, I'd like to know all potential nested issues and I will try to solve it if possible. But the problem is that I am not clear about those issues that you guys mentioned. Is there any thread talk about them?
I think I was thinking along the lines of what I wrote in this thread:
Msg-ID <52E28EFB.3020008@eu.citrix.com>
It seems there the minimum thing for a "1.0" release is that an L1 admin
must not be able to do anything to affect an L0; and thinks at the
moment likely to do so are enabling PoD (and probably also paging) for
L2 guests. It's OK if enabling PoD crashes the *L1* hypervisor (because
that's under the L1 admin's control); but it must not be allowed to
crash / DoS the L0 hypervisor.
-George
>
>> issue. (On my to-do list is to collect these somewhere so we have a
>> clear set of criteria for moving nested HVM from "tech preview" to
>> "supported".)
> Yes, it makes sense.
>
>> It would be good to put something in the release note, however, to say
>> how much it has progressed. I'll see what I can do.
> Yes, nested was moving forward in last year. It's better to tell this to people since lots of people unaware of this feature.
>
>> -George
>
> Best regards,
> Yang
>
>
next prev parent reply other threads:[~2014-03-14 17:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 2:58 Please review the key 4.4 release docs Russell Pavlicek
2014-03-10 4:27 ` Zhang, Yang Z
2014-03-10 9:54 ` George Dunlap
2014-03-10 10:42 ` Russell Pavlicek
2014-03-10 10:58 ` George Dunlap
2014-03-10 11:05 ` George Dunlap
2014-03-10 11:09 ` Russell Pavlicek
2014-03-10 12:35 ` George Dunlap
2014-03-10 12:39 ` Russell Pavlicek
2014-03-10 12:45 ` George Dunlap
2014-03-10 13:06 ` Russell Pavlicek
2014-03-10 11:18 ` Russell Pavlicek
2014-03-10 11:22 ` George Dunlap
2014-03-10 11:27 ` George Dunlap
2014-03-10 12:01 ` David Vrabel
2014-03-10 12:05 ` Russell Pavlicek
2014-03-10 12:02 ` Russell Pavlicek
2014-03-11 1:23 ` Zhang, Yang Z
2014-03-14 17:24 ` George Dunlap [this message]
2014-03-14 17:43 ` George Dunlap
2014-03-17 1:04 ` Zhang, Yang Z
-- strict thread matches above, loose matches on Subject: below --
2014-03-10 13:26 Konrad Rzeszutek Wilk
2014-03-10 13:28 ` Russell Pavlicek
2014-03-10 13:34 ` Jan Beulich
2014-03-10 14:21 ` Russell Pavlicek
2014-03-10 16:32 ` Konrad Rzeszutek Wilk
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=53233B59.8080208@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=russell.pavlicek@citrix.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.