From: Rusty Russell <rusty@rustcorp.com.au>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: lguest problem on boot of guest kernel
Date: Sat, 02 Jun 2007 20:27:39 +1000 [thread overview]
Message-ID: <1180780059.9228.72.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.60.0706011704240.786@rtl14.hofr.at>
On Fri, 2007-06-01 at 17:25 +0200, Nicholas Mc Guire wrote:
> Hi !
>
> Kenrel 2.6.21 (kernel.org)
> Patch lguest-2.6.21-254.patch
> Distro Slackware 11.0
> GCC 3.4.6
> GLIBC 2.3.6
> HW model name : AMD Duron(tm) procu{s{
>
>
> Module Size Used by
> tun 7680 0
> lg 54600 0
>
>
> just started playing with lguest - patching, compiling and booting the
> host-kernel goes ok - compiling lguest is ok as well after hardcodeing
> SIOCBRADDIF - but on the first boot attempt of a guest linux I get:
>
> root@darkstar:/usr/src/linux-2.6.21# Documentation/lguest/lguest
> 64m vmlinux --tunnet=192.168.2.1 --block=../root_fs root=/dev/lgba
> lguest: unhandled trap 6 at 0xc0117903 (0x0)
>
> this should be in "c01178db T reserve_top_address" - any idea what could
> be wrong ?
Hi Nicholas!
You're the second one to hit this in as many days. I just uploaded an
updated patch, but the summary is that you have to turn off COMPAT_VDSO
for the 2.6.21 patch. (You can actually leave it on in the host, it's
just the guests...)
Thanks for the bug report!
Rusty.
next prev parent reply other threads:[~2007-06-02 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 15:25 lguest problem on boot of guest kernel Nicholas Mc Guire
2007-06-02 10:27 ` Rusty Russell [this message]
2007-06-02 13:24 ` Nicholas Mc Guire
2007-06-08 7:27 ` lguest/host benchmarks Nicholas Mc Guire
2007-06-09 4:16 ` Rusty Russell
2007-06-09 4:27 ` Glauber de Oliveira Costa
2007-06-09 4:28 ` Nicholas Mc Guire
2007-06-09 4:44 ` Nicholas Mc Guire
2007-06-09 10:43 ` 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=1180780059.9228.72.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=der.herr@hofr.at \
--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;
as well as URLs for NNTP newsgroup(s).