Subject: Re: [vserver] testme.sh failed in Ubuntu 7.04 with kernel 2.6.21.6, vserver patch 2.2.0.3
From: "Î޼ɺØ" <wolfhe.zz@gmail.com>
Date: Fri, 10 Aug 2007 16:26:03 +0800
Fri, 10 Aug 2007 16:26:03 +0800
Hi everyone,

Thanks a lot for your quick responses!

I downloaded the util-vserver 0.30.213 (it seems it's the latest stable
release) and built it with dietlibc and NOLEGACY option. However, the
testme.sh still reported the same problems: chcontext got segment-fault and
chbind failed.

Besides, I also tried using 2.6.21.6 linux kernel with 2.2.0.1 vserver
patch, util-vserver 0.30.212 and the problems kept the same as before.

What I want to do is to use VPS to build a testbed for some p2p and/or
cluster applications.

Thanks again for your guys' kind help!

Best Regards,

He Jin

2007/8/9, Daniel Hokka Zakrisson <daniel@hozac.com>:
>
> Corey Wright wrote:
> > <snip>
> >
> > i believe you need util-vserver >= 0.30.213 for vserver kernel patch
> > 2.2.0.3 (due to the disabling of legacy support in kernel patch used by
> > previous util-vserver versions).  that's all just from my memory of
> > reading
> > this list, so i could be remembering wrong (but worth a try).
>
> It's just a recommendation. util-vserver 0.30.213+ will automatically
> handle the assignment of a static context id for you (for new guests),
> with any previous version you'd have to handle it manually.
>
> > i can't find confirmation anywhere on the linux-vserver.org website
> except
> > for  this "recommendation" by daniel (which i initially found in my
> > personal email archive):
> > http://archives.linux-vserver.org/200704/0007.html.
> >
> > Herbert, Daniel, Benedikt: is the minimum util-vserver version required
> > for
> > each vserver kernel patch release documented anywhere on
> linux-vserver.org
> > (as i couldn't find anything within 5 to 10 minutes of
> > searching/browsing).
>
> As the kernel and utils are massively backwards-compatible, you're pretty
> much supposed to be able to run any combination of kernel and utils and
> have it at least semi-work. The latest utils are of course always
> recommended, and that's most likely what you'll need if you want to use
> all the features of a recent kernel.
>
> --
> Daniel Hokka Zakrisson
>


Hi everyone,

Thanks a lot for your quick responses!

I downloaded the util-vserver 0.30.213 (it seems it's the latest stable release) and built it with dietlibc and NOLEGACY option. However, the testme.sh still reported the same problems: chcontext got segment-fault and chbind failed.

Besides, I also tried using 2.6.21.6 linux kernel with 2.2.0.1 vserver patch, util-vserver 0.30.212 and the problems kept the same as before.

What I want to do is to use VPS to build a testbed for some p2p and/or cluster applications.

Thanks again for your guys' kind help!

Best Regards,

He Jin

2007/8/9, Daniel Hokka Zakrisson <daniel@hozac.com>:
Corey Wright wrote:
> <snip>
>
> i believe you need util-vserver >= 0.30.213 for vserver kernel patch
> 2.2.0.3 (due to the disabling of legacy support in kernel patch used by
> previous util-vserver versions).  that's all just from my memory of
> reading
> this list, so i could be remembering wrong (but worth a try).

It's just a recommendation. util-vserver 0.30.213+ will automatically
handle the assignment of a static context id for you (for new guests),
with any previous version you'd have to handle it manually.

> i can't find confirmation anywhere on the linux-vserver.org website except
> for  this "recommendation" by daniel (which i initially found in my
> personal email archive):
> http://archives.linux-vserver.org/200704/0007.html.
>
> Herbert, Daniel, Benedikt: is the minimum util-vserver version required
> for
> each vserver kernel patch release documented anywhere on linux-vserver.org
> (as i couldn't find anything within 5 to 10 minutes of
> searching/browsing).

As the kernel and utils are massively backwards-compatible, you're pretty
much supposed to be able to run any combination of kernel and utils and
have it at least semi-work. The latest utils are of course always
recommended, and that's most likely what you'll need if you want to use
all the features of a recent kernel.

--
Daniel Hokka Zakrisson