Yuji Nishida wrote: > Hi all, > > This could help my previous mail. > > I wanted to create new guest of F8. > But then util-vserver on my box couldn't create a guest of that > distribution. > > That page in qutation meant to do this. > cp -a /usr/lib/util-vserver/distribution/fc6 /etc/ > vserver/.distribution/f8 > Then I changed the yum configuration for new distribution. If it's not complaining about the missing distribution, it _could_ create a guest of that distribution. That could easily be confirmed by looking at the output of the build. > After doing that, any warning or caution didn't appear when vserver > created a guest of new distribution. > But it apparently had failed to create it because status of the guest > was still "stopped" after starting the vserver guest. Fedora 8 renamed the syslog daemon, so you have to change the redhat initpost script to exclude rsyslog as well as syslog from being chkconfig'ed off. util-vserver 0.30.215 will fix it... > Thanks. > > ----- > Yuji Nishida > nishidy@nict.go.jp > > Begin forwarded message: >> >> Hi all, >> >> Summary: I want to know two things. >> 1)How to register new distribution? >> 2)Where can I find vserver log? >> >> Environment: >> # 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 >> >> >> I want to register new distribution for vserver guest. >> I refered to this page >> (http://archives.linux-vserver.org/200507/0140.html >> ) >> and did it. But vserver guest couldn't start correctly. >> I executed to do it with verbose option but the output was not >> enough to understand what's going on. >> Also, I have not found vserver log of starting the guest in my box. >> If I had that, I could look into it by myself. >> >> This is all what vserver showed me at starting guest of new >> distribution. >> #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 in advance. >> >> ----- >> Yuji Nishida >> nishidy@nict.go.jp > -- Daniel Hokka Zakrisson