From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 01/12] Nested Virtualization: tools
Date: Fri, 1 Apr 2011 10:41:58 +0200 [thread overview]
Message-ID: <4D958FD6.7040706@amd.com> (raw)
In-Reply-To: <19860.50935.146868.916017@mariner.uk.xensource.com>
On 03/31/11 20:24, Ian Jackson wrote:
> Christoph Egger writes ("[Xen-devel] [PATCH 01/12] Nested Virtualization: tools"):
>> tools: Add nestedhvm guest config option
>
> I don't have an objection to this. The tools parts seem largely sane.
> However, I have two queries.
>
> Firstly, one for Christoph: is this patch safe to apply before the
> relevant hypervisor features, or will it break ? If it will break
> then it should be applied later.
It is safe. nested virtualization is disabled by default. You have to
add "nestedhvm=1" to your guest config file to make the guest see
hw virtualization available.
> Secondly, one for the Xen.org team in general: are we accepting new
> features in Xend ? If not then I should drop the changes to xend from
> this patch.
>
> Ian.
>
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-04-01 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 14:22 [PATCH 01/12] Nested Virtualization: tools Christoph Egger
2011-03-28 13:54 ` Dong, Eddie
2011-03-31 18:24 ` Ian Jackson
2011-04-01 8:41 ` Christoph Egger [this message]
2011-04-01 10:26 ` Keir Fraser
2011-04-04 10:25 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2010-12-20 16:03 Christoph Egger
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=4D958FD6.7040706@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).