Hi Chuck
I've been running 2.6.22.18-vs2.3.0.32 for about 3 months with no issues.
IIRC my preexisting vserver guests did not require any modification to run.
I also wonder why this code is not yet in 'stable'..
cheers,
Jason
Chuck wrote:
> we finally have a need for a true 127.0.0.1 inside a vserver :(
>
> we are presently running 2.6.20-vs2.2.0-gentoo on this amd64 host with 100+
> virtual servers running.
>
> according to what i have been reading in this list, i have to upgrade to
> the 'gentoo unstable' 2.3.0.29 or .34 versions to enable true localhost. is
> there any workaround using our existing installation? this particular vserver
> cannot use a remapped localhost to the primary ip. it must be a private
> 127.0.0.1.
>
> 1. would this upgrade be compatible with existing vservers? i do not wish to
> update every one of them.
>
> 2. i am not very happy about putting unstable code on a production machine. is
> this code ready for production yet? if so why has gentoo not unmasked it?
>
>
>
Received on Tue May 27 01:09:57 2008