From: Mike Tierney (miket_at_marketview.co.nz)
Date: Sat 18 Jun 2005 - 12:50:51 BST
> -----Original Message-----
> From: vserver-bounces_at_list.linux-vserver.org [mailto:vserver-
> bounces_at_list.linux-vserver.org] On Behalf Of Oliver Dietz
> Sent: Saturday, 18 June 2005 10:09 p.m.
> To: vserver_at_list.linux-vserver.org
> Subject: Re: [Vserver] Suse and Yast inside VServer
> Hi Mike,
> > I use SuSE SLES 9 guests, except I cheated.
> Wow, thats great! Exactly what i need!
> i've tried that one week ago (with suse 9.2 prof.) ...
> (1) made 2 partitions
> (2) installed suse to each partition (making 2 minimal installations)
> (3) used the one as vserver-host, the other as a template for a vserver
> (4) deploy-vserver ... skeleton
> (5) copied the template to there
> (6) replaced fstab
> (7) done some thinks i don't remind
Yep I think 7) is where the problem is :) Luckily I remember what I did....
mostly! The main problems are because of the way SuSE init works.
1) edit the main init script /vservers/<foo>/etc/init.d/rc and after the
initial comment, add:
2) edit the /vservers/<foo>/etc/init.d/network script and put some "exit
0"'s in it. Otherwise you get a hang on vserver startup/shutdown when the
guest tries to flush the interfaces/addresses or something.
I think last time I said this, someone asked me "Why not just chkconfig
network off?" Well if you do that then all the other services that *depend*
on "network" being turned on, wont run. This is because SuSE uses innserv(?)
or something. This problem doesn't happen on other distro's I don't think
(except Gentoo?? /shrug)
Hope this helps!
If you still don't have any luck, let me know and I'll have a closer look at
my vserver guest image.
Vserver mailing list