From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: George Dunlap <george.dunlap@eu.citrix.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: Thu, 13 Feb 2014 11:29:42 +0100 [thread overview]
Message-ID: <1392287382.32038.34.camel@Solace> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0A9DAE1E@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 2014 bytes --]
[Adding the Xen publicity mailing list]
On gio, 2014-02-13 at 03:55 +0000, Zhang, Yang Z wrote:
> Hi George,
>
> I have updated the Latest Xen nested status in the Xen wiki page, please have a look.
>
Hey Yang,
This is something really useful to have on the wiki, thanks for doing
it.
> Although it is hard to say nested is good supported or product quality, it is ready to let people to know nested basically is supported by Xen.
>
Right. With that in mind, I think this topic would be a great one for a
blog post on the Xen Project's blog! The content you have on the wiki is
mostly fine as the core content of the blog post too, we'd just need a
couple more "colloquial" glue paragraph here and there, both about
nested virt in general and about Xen supporting it, for instance...
> Especially, for Xen on Xen case, I didn't see any issue with it for more than half of year. Besides, I am always using nested Xen to debug Xen booting issue which doesn't need to reboot my real box. And it really helps me a lot.
>
...something like this line above... It's actually a quite good example
of what I meant above! :-)
So, how do you feel about this?
> So, if possible, I hope we can add nested support into Xen 4.4 release to let people know current status.
>
Sorry for my ignorance on the subject, what is it that is missing for
making the above (and the content of the wiki) true for 4.4?
Anyway, I don't think that, whatever the answer is, it will be less
worth to have a blog post about nested virt... At most it will affect
when we want it. If it's going to be a 4.4 feature, I think the sooner
the better. If not, we can wait a little bit.
Let me know your thoughts on the idea.
Regards,
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
next prev parent reply other threads:[~2014-02-13 10:29 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 [this message]
2014-02-14 1:13 ` Zhang, Yang Z
2014-02-14 10:24 ` George Dunlap
2014-02-14 14:40 ` Dario Faggioli
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=1392287382.32038.34.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).