From: Rusty Russell <rusty@rustcorp.com.au>
To: Matt Mackall <mpm@selenic.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: [RELEASE] Lguest for 2.6.21
Date: Fri, 04 May 2007 10:43:09 +1000 [thread overview]
Message-ID: <1178239389.23670.33.camel@localhost.localdomain> (raw)
In-Reply-To: <1178237603.23670.26.camel@localhost.localdomain>
On Fri, 2007-05-04 at 10:13 +1000, Rusty Russell wrote:
> On Thu, 2007-05-03 at 11:02 -0500, Matt Mackall wrote:
> > On Thu, May 03, 2007 at 12:43:48AM +1000, Rusty Russell wrote:
> > > http://lguest.ozlabs.org/lguest-2.6.21-254.patch.gz
> > >
> > > See Documentation/lguest/lguest.txt for how to run,
> > > drivers/lguest/README for the draft code documentation journey.
> >
> > Your lguest readme is quite lacking in the area of how to configure a
> > guest kernel as opposed to the host kernel. More hand-holding, please.
>
> Hi Matt!
>
> Ah, that's because they are the same kernel. Turning on CONFIG_LGUEST
> builds-in the parts needed to be a guest as well.
>
> Thanks for pointing out that weakness. I will modify lguest.txt to make
> that clear.
Something like this:
diff -r 940ec1c6ac5a Documentation/lguest/lguest.txt
--- a/Documentation/lguest/lguest.txt Thu May 03 23:00:19 2007 +1000
+++ b/Documentation/lguest/lguest.txt Fri May 04 10:17:23 2007 +1000
@@ -23,7 +23,10 @@ Developer features:
Running Lguest:
-- You will need to configure your kernel with the following options:
+- Lguest runs the same kernel as guest and host. You can configure
+ them differently, but usually it's easiest not to.
+
+ You will need to configure your kernel with the following options:
CONFIG_HIGHMEM64G=n ("High Memory Support" "64GB")[1]
CONFIG_TUN=y/m ("Universal TUN/TAP device driver support")
Cheers,
Rusty.
next prev parent reply other threads:[~2007-05-04 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 14:43 [RELEASE] Lguest for 2.6.21 Rusty Russell
2007-05-02 19:33 ` WANG Cong
2007-05-02 19:59 ` WANG Cong
2007-05-02 23:00 ` Rusty Russell
2007-05-03 3:57 ` WANG Cong
2007-05-03 4:20 ` Rusty Russell
2007-05-03 5:43 ` WANG Cong
2007-05-03 16:02 ` Matt Mackall
2007-05-04 0:13 ` Rusty Russell
2007-05-04 0:43 ` Rusty Russell [this message]
2007-05-04 3:20 ` Matt Mackall
2007-05-04 3:39 ` Rusty Russell
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=1178239389.23670.33.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=virtualization@lists.linux-foundation.org \
/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