Re: [Vserver] vserver guest sharing the eth0 of host
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
Re: [Vserver] Re: forcedeth module for 2.6.14-amd64-smp-vs
Matvey Gladkikh schrieb: On 19/04/06 18:22 +0200, Eugen Leitl wrote: I'm running 2.6.14-amd64-smp-vs on a Sun Fire X2100. Unfortunately, 2.6.14-amd64-smp-vs lacks the forcedeth module, so only the Broadcom NIC is usable. I didn't catch this in time to try building my own 2.6.14-amd64-smp-vs Does anyone here have a new Debian package for 2.6.14-amd64-smp-vs or a similiar vs version of an AMD64 kernel? May be you wish to build debian kernel like a mainstream with all include? 1. Install 2.6.14-amd64-smp kernel 2. Download source package for 2.6.14-amd64-smp 3. cat /boot/config.2.6.14-amd64-smp /usr/src/2.6.14-amd64-smp/.config cd /usr/src/2.6.14-amd64-smp/ patch -p1 2.6.14-vs-patch make oldconfig make menuconfig (to check modules) 4. (later I used make-kpkg --initrd kernel-image and build my own kernel with ONLY difference to debian kernel - vserver applied ) I ve done this for i386 2.6.12 kernel - you can try for your one. It is not very good to make kernels with reduced ammount of drivers - because they will not be portable across different hardware. If you have no compiler on the server you may like the debian backport kernels read more on http://www.backports.org/instructions.html . Greets Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: forcedeth module for 2.6.14-amd64-smp-vs
Matvey Gladkikh schrieb: On 19/04/06 18:22 +0200, Eugen Leitl wrote: May be you wish to build debian kernel like a mainstream with all include? 1. Install 2.6.14-amd64-smp kernel 2. Download source package for 2.6.14-amd64-smp 3. cat /boot/config.2.6.14-amd64-smp /usr/src/2.6.14-amd64-smp/.config cd /usr/src/2.6.14-amd64-smp/ patch -p1 2.6.14-vs-patch make oldconfig make menuconfig (to check modules) if you want to do it manual, but use the kpgk, you may cd /usr/src/linux ../kernel-patches/all/apply/vserver 4. (later I used make-kpkg --initrd kernel-image and build my own kernel with ONLY difference to debian kernel - vserver applied ) I ve done this for i386 2.6.12 kernel - you can try for your one. That exactly, how I do my kernels - but I want them to be as small and simple as possible. It is not very good to make kernels with reduced ammount of drivers - because they will not be portable across different hardware. Whatever module is laying around may bring a security risk, that's why I use only few modules. A missing module can not be loaded. Some, like me, do not need this kernel on _every_ Hardware but *only* on server machines (btw they compile a lot quicker). greets Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] forcedeth module for 2.6.14-amd64-smp-vs
Eugen Leitl schrieb: I'm running 2.6.14-amd64-smp-vs on a Sun Fire X2100. Unfortunately, 2.6.14-amd64-smp-vs lacks the forcedeth module, so only the Broadcom NIC is usable. I didn't catch this in time to try building my own 2.6.14-amd64-smp-vs Does anyone here have a new Debian package for 2.6.14-amd64-smp-vs or a similiar vs version of an AMD64 kernel? Thanks much. ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver Maybe you want to give my personal latest a try http://helpdesk.std-service.de/kernel-image-2.6.15-amd64-smp-vs_0.94_amd64.deb (still very reduced modules, but most network drivers). Greets Markus -- https://www.std-soft.com/FC8B22FC.pdf ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Invalid Release file, no entry for main/binary-amd64/Packages
Eugen Leitl schrieb: However, when trying to build a vserver I'm running into the bug described at http://savannah.nongnu.org/bugs/?func=detailitemitem_id=13844 I presume it's an apt sources problem, since debootstrap --arch amd64 sarge /pure64/ http://amd64.debian.net/debian-amd64/ completes fine. What should I stick where to make it work? I'm using a modified (but undocumented) version of the original script: http://helpdesk.std-service.de/newvserver.txt next setup your /etc/vservers/newvserver-vars to meet your needs: example: 8--- # Configuration file for newvserver # See man newvserver for the variables that you can set here. # Default VROOTDIR VROOTDIR=/etc/vservers/.defaults/vdirbase INTERFACE=br0 MIRROR=http://ftp.de.debian.org/debian-amd64/debian; . . . 8--- hth Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] debian AMD64 kernel package; host template manipulation
Eugen Leitl schrieb: I've gotten reasonably comfortable with manual instantiation of vserver guests, and would like to start manipulating them by scripts. A few questions for my basic understanding: 1) if I vserver vXY stop, can I package the static directory with tar and copy it somewhere/rsync it someplace else, will the entire state will be saved? Including e.g. PostgreSQL dbases, or will I have to make a dump and reimport afterwards? Which files context is still missing (which directories would I also have to rsync?) Definitifely, everything will remain ok. If rsyncing - go for the -H and --numeric-ids switches, especially when changing the hosts distri. 3) Are there any existing scripts to migrate a running guest to a different server? A simple way would be to do a variation of question 1). Can I make vserver guests live on a NFS partition? Lustre? PVFS? Is there a way of keeping two running guest instances synchronous, save of a HA/drbd based setup? (I have some very basic understanding of it, just enough for a HA NFS system). I realize some snapshot/migration functionality for clusters is being worked on -- how far is this removed from production? Using debian pkg util-vserver you'll find vserver-copy wich does all you needs. hth Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] What can be the reason when I see all interfaces in a vserver?
Hi *, in a vserver I see all interfaces plus their coresponding ip's. example: [...] eth1:m47 Link encap:Ethernet HWaddr 00:E0:81:05:32:D7 inet addr:10.96.66.47 Bcast:10.96.66.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:11 Base address:0x5000 eth1:m53 Link encap:Ethernet HWaddr 00:E0:81:05:32:D7 inet addr:10.96.66.2 Bcast:10.96.66.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:11 Base address:0x5000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:990 errors:0 dropped:0 overruns:0 frame:0 TX packets:990 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:120970 (118.1 KiB) TX bytes:120970 (118.1 KiB) [EMAIL PROTECTED]:/ [...] What I did before taht was updating the kernel from a 2.4.26 ctx to a 2.6.8 vs. How can I avoid this? Greets Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Did anybody attach a VServer to a eth0/tap0 or br0 ?
Hi *, in searching for information how to bind to a virtual device directly (or should i better say: use the device directly) without the dev:vsname nor dev.vlan convention I could not find any hints. I want to use an extra interface only for one vserver and I#d prefer the tun/tap devices for their unique mac adress. Are here any ideas? Thanks Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Re: chbind with multihomed hosts
Thnx Herbert, so I'll remain using iproute2 and the rt_tables in a past vserver start proc for now. greets Markus Herbert Poetzl schrieb: On Sat, Jan 08, 2005 at 04:27:12PM +0100, Markus Neubauer wrote: Hi *, Hey Markus! how can I solve a problem on multihomed hosts with their broadcast? I would say you can not solve this atm without heavy hacking or special tricks ... this should be easy with ngnet, which is currently being developed (so it's not nearly production quality yet) best, Herbert When setting up a virtual host with 2 interfaces, the last with the syntax ethn:1.2.3.4/255.255.255.n is winning the broadcast address. The following table should clearify my question, as one can see the broadcast for the first interface is wrong in the virtual bcast addressing: The full setup of the host is (I shortened the list): | - | eth0 | Link encap:Ethernet HWaddr XX:B0:81:A5:7F:54 |inet addr:192.168.5.168 Bcast:192.168.5.255 Mask:255.255.255.0 | ... | | eth0:m461 Link encap:Ethernet HWaddr XX:B0:81:A5:7F:54 | inet addr:192.168.5.146 Bcast:10.11.12.255 Mask:255.255.255.0 | ??? | ... | 2. Interface | eth1 Link encap:Ethernet HWaddr XX:B0:81:A5:7F:55 | inet addr:10.11.12.71 Bcast:10.11.12.255 Mask:255.255.255.0 ... | | eth1:m46 Link encap:Ethernet HWaddr XX:B0:81:A5:7F:55 | inet addr:10.11.12.46 Bcast:10.11.12.255 Mask:255.255.255.0 ... | -- Any Ideas ? Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] Re: chbind with multihomed hosts
Hi *, how can I solve a problem on multihomed hosts with their broadcast? When setting up a virtual host with 2 interfaces, the last with the syntax ethn:1.2.3.4/255.255.255.n is winning the broadcast address. The following table should clearify my question, as one can see the broadcast for the first interface is wrong in the virtual bcast addressing: The full setup of the host is (I shortened the list): | - | eth0 | Link encap:Ethernet HWaddr XX:B0:81:A5:7F:54 |inet addr:192.168.5.168 Bcast:192.168.5.255 Mask:255.255.255.0 | ... | | eth0:m461 Link encap:Ethernet HWaddr XX:B0:81:A5:7F:54 | inet addr:192.168.5.146 Bcast:10.11.12.255 Mask:255.255.255.0 | ??? | ... | 2. Interface | eth1 Link encap:Ethernet HWaddr XX:B0:81:A5:7F:55 | inet addr:10.11.12.71 Bcast:10.11.12.255 Mask:255.255.255.0 ... | | eth1:m46 Link encap:Ethernet HWaddr XX:B0:81:A5:7F:55 | inet addr:10.11.12.46 Bcast:10.11.12.255 Mask:255.255.255.0 ... | -- Any Ideas ? Markus ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
