ADNET Ghislain schrieb: > Hi, > > I am testing vserver and all works well for me but one thing. I have > a server with one public IP. I use vserver to have 2 vserver, one is > the prod one and the other is a test one. I start one after stopping > the other (they never runs at the same time). I have a problem in the > fact that i use the eth0 of the host for both of them. > > My issue is that when i shut down one of the vserver it shutdown > completly the eth0 interface of the Host... I really find the > documentation troubling. This patchwork of different "how-to", "faq" > and articles is really hard to grasp for a new user of vserver. > > > to come back on my problem: > > > /usr/src/util-vserver-0.30.210# vserver mailservertest stop > Stopping periodic command scheduler: cron. > Stopping ClamAV daemon: clamd > Stopping ClamAV virus database updater: freshclam > Stopping MTA: exim4. > Stopping internet superserver: inetd. > Stopping SpamAssassin Mail Filter Daemon: spamd. > Saving the System Clock time to the Hardware Clock... > hwclock is unable to get I/O port access: the iopl(3) call failed. > Hardware Clock updated to Tue May 9 19:52:31 UTC 2006. > Stopping deferred execution scheduler: atd. > Stopping kernel log daemon: klogd. > Stopping system log daemon: syslogd. > Sending all processes the TERM signal...done. > Sending all processes the KILL signal...done. > Saving random seed...done. > Unmounting remote and non-toplevel virtual filesystems...done. > Deconfiguring network interfaces...done. > Cleaning up ifupdown...done. > Deactivating swap...umount: none: not found > umount: /tmp: must be superuser to umount > Not superuser. > done. > Unmounting local filesystems...umount: none: not found > umount: /tmp: must be superuser to umount > umount: /dev/hdv1: not found > umount: /: not mounted > done. > mount: permission denied > Rebooting... ifdown: shutdown eth0: Permission denied > :/usr/src/util-vserver-0.30.210# > > > > at this point the server loose the network. i have not the "Enable > different security models" setup as the FAQ says. I do not see > anything special, any hints ? > > > -- > Cordialement, > Ghislain ADNET. > > > # vserver-info > Versions: > Kernel: 2.6.16.11-vs2.0.2-rc18 > VS-API: 0x00020001 > util-vserver: 0.30.210; May 9 2006, 21:43:40 > > Features: > CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-13) > CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-13) > CPPFLAGS: '' > CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W' > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W > -fmessage-length=0' > build/host: i686-pc-linux-gnu/i686-pc-linux-gnu > Use dietlibc: no (you have been warned) > Build C++ programs: yes > Build C99 programs: yes > Available APIs: v13,net > ext2fs Source: e2fsprogs > syscall(2) invocation: fast > vserver(2) syscall#: 273/glibc > > Paths: > prefix: /usr/local > sysconf-Directory: ${prefix}/etc > cfg-Directory: ${prefix}/etc/vservers > initrd-Directory: $(sysconfdir)/init.d > pkgstate-Directory: ${prefix}/var/run/vservers > vserver-Rootdir: /vservers Your trouble might get solved when you touch a file with the name nodev in the interface dir of the corresponding interface.
Example: touch /etc/vservers/<guestname>/interfaces/0/nodev That will avoid ifconfig for the defined interface. hth Markus _______________________________________________ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver