On Thu August 20 2009, Michael wrote: > Hi all, > > I'am having a strage problem of losing eth0 in guest if any guest shutdown. > > Host eth0 10.1.1.13 > guest1 192.168.1.21 > guest2 192.168.1.22 > guest3 192.168.1.23 > > after start all guest all guest works fine , but after vserver guest1 stop, > guest2 and guest3 have no more eth0. > > then start guest1 - only guest1 have eth0. > > if start guest3 first, then guest1(2) and stop guest3 - then guest1 > and guest2 have no eth0. > Where to dig? > FAQ 5.6: http://linux-vserver.org/Frequently_Asked_Questions#If_I_shut_down_my_vserver_guest.2C_the_whole_Internet_interface_ethX_on_the_host_is_shut_down.__What_happened.3F > > when using for guest ips 10.1.1.xx all works as expected. > > > > Versions: > Kernel: 2.6.30.5-vs2.3.0.36.14-pre5 > VS-API: 0x00020304 > util-vserver: 0.30.216-pre2841; Aug 21 2009, 12:04:50 > > Features: > CC: gcc, gcc (Debian 4.3.2-1.1) 4.3.2 > CXX: g++, g++ (Debian 4.3.2-1.1) 4.3.2 > CPPFLAGS: '' > CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W -funit-at-a-time' > CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W > -fmessage-length=0 -funit-at-a-time' > build/host: x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu > Use dietlibc: yes > Build C++ programs: yes > Build C99 programs: yes > Available APIs: v13,net,v21,v22,v23,netv2 > ext2fs Source: kernel > syscall(2) invocation: alternative > vserver(2) syscall#: 236/glibc > crypto api: beecrypt > python bindings: no > use library versioning: yes > > Paths: > prefix: /usr > sysconf-Directory: /etc > cfg-Directory: /etc/vservers > initrd-Directory: $(sysconfdir)/init.d > pkgstate-Directory: /var/run/vservers > vserver-Rootdir: /vservers > >