[Planetlab-devel] Re: eth0 is not configured corretly

[Thierry Parmentelat]

Hi Yuji

I have recently started deploying centos 5.1 boxes, and have taken  
advantage of that to document and clean a bit how to install these  
vserver-capable boxes, and how to link them to local fedora mirrors

It's mostly a best effort initiative but you might find that useful :
https://svn.planet-lab.org/wiki/VserverCentos
if you happen to have an account on planet-lab.org, please feel free  
to enrich or tweak as you see fit

Besides, the issues about rsyslogd should also be fixed now.

-- Thierry

On Mar 9, 2008, at 9:56 AM, Yuji Nishida wrote:

> Hi Thierry and Marc,
>
> Now we have private PlanetLab environment here.
> Still its build environment is on Fedora.
>
> Please be sure that Fedora8 named syslog as rsyslog.
> That caused some problems when creating vserver guest and running  
> MyPLC.
>
> Regards,
>
> -----
> Yuji Nishida
> nishidy at nict.go.jp
>
> On 2008/02/26, at 23:28, Thierry Parmentelat wrote:
>
>> Hi Yuji
>>
>> It's right that setting up all the necessary stuff correctly for  
>> vserver to behave according to our needs on fc6 is a tedious process
>>
>> Please note that, as discussed on another thread of this list, the  
>> trend is to have the build boxes setup under centos, on which as it  
>> seems, setting up all this is much simpler.
>>
>> As far as I am concerned, I have a new build box ordered and will  
>> install it under centos5 as well
>>
>> If this is an option for you, I would strongly recommend you to  
>> consider it
>>
>> ====
>> in any case, here is what I get under my build box
>>
>> root at onelab-build ~ # cat /etc/redhat-release
>> Fedora Core release 6 (Zod)
>>
>> root at onelab-build ~ # uname -a
>> Linux onelab-build.inria.fr 2.6.20-1.2949.fc6.vs2.2.0.3.1 #1 SMP  
>> Sun Jul 22 15:55:02 EDT 2007 i686 i686 i386 GNU/Linux
>>
>> root at onelab-build ~ # rpm -q kernel
>> kernel-2.6.22.4-45.fc6
>> kernel-2.6.20-1.2949.fc6.vs2.2.0.3.1
>>
>> root at onelab-build ~ # rpm -aq | grep util-vserver
>> util-vserver-lib-0.30.214.rpmfake-0.1
>> util-vserver-debuginfo-0.30.214.rpmfake-0.1
>> util-vserver-devel-0.30.214.rpmfake-0.1
>> util-vserver-legacy-0.30.214.rpmfake-0.1
>> util-vserver-core-0.30.214.rpmfake-0.1
>> util-vserver-build-0.30.214.rpmfake-0.1
>> util-vserver-0.30.214.rpmfake-0.1
>> util-vserver-sysv-0.30.214.rpmfake-0.1
>>
>> root at onelab-build ~ # rpm -q yum
>> yum-3.0.6-1.fc6
>>
>> ====
>> in the hope that it can be useful to you - and on a best effort  
>> basis - I have tried to gather the stuff that I've used here:
>> http://build.one-lab.org/build-fc6/
>>
>> you'll find a few useful rpms for fc6
>>
>> I have also stored there {fc6,f8}yumconfig.tar (that I provided  
>> already) and that describe the contents of the yum config as stored  
>> in /etc/vservers/.distributions,
>>
>> please pay attention to f8-distributions.tar that holds the  
>> contents of /usr/lib/util-vserver/distributions/f8 that is missing  
>> in the fc6 rpm of util-vserver-build rpm.
>>
>> ====
>> I hope this helps -- Thierry
>>
>> On Feb 25, 2008, at 12:09 PM, Yuji Nishida wrote:
>>
>>> Hi Thierry,
>>>
>>> Since we still have some problem in running F8 vserver guest  
>>> inside F6 host, we decided to use exactly the same setting as you  
>>> guys do.
>>> What version of kernel and util-vserver do you run?
>>>
>>> Here is what we have.
>>>
>>> # uname -a
>>> Linux node7 2.6.22.10-vs2.2.0.5 #1 SMP Wed Feb 6 00:49:00 JST 2008  
>>> i686 i686 i386 GNU/Linux
>>>
>>> # vserver --version
>>> vserver 0.30.214 -- manages the state of vservers
>>> This program is part of util-vserver 0.30.214
>>>
>>> We have not successfully created F8 vserver guest yet.
>>> I consulted this page (http://archives.linux-vserver.org/200507/0140.html 
>>> ) but vserver guest did not start correctly.
>>> I executed the command with verbose option but the output was not  
>>> enough to show what's going on.
>>> Also, I could not find a vserver log.
>>>
>>> This is all what vserver showed me in starting F8 guest
>>> #vserver -v guest start
>>> New network context is 40034
>>> Adding
>>> New security context is 40034
>>>
>>> If vserver starts correctly, I could find these output below.
>>> Starting system logger: ...
>>> Starting kernel logger: ...
>>>
>>> Thanks.
>>>
>>> -----
>>> Yuji Nishida
>>> nishidy at nict.go.jp
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at lists.planet-lab.org
>>> https://lists.planet-lab.org/mailman/listinfo/devel
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.planet-lab.org
>> https://lists.planet-lab.org/mailman/listinfo/devel
>
> _______________________________________________
> Devel mailing list
> Devel at lists.planet-lab.org
> https://lists.planet-lab.org/mailman/listinfo/devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.planet-lab.org/pipermail/devel/attachments/20080309/e7786a15/attachment.html