From: Gilles (gilles_at_harfang.homelinux.org)
Date: Tue 19 Oct 2004 - 16:57:01 BST
Hello.
> Just a last mail to explain that all my preview questions are around a
> (big) mistake, and perhaps it could be interesting for someone who start
> with vserver and kernel 2.6.
I was just about to post a request for help about 2.6.x.
I use Debian testing/unstable and the following deb packages:
- kernel-package (to patch/compile new kernels: currently, 2.6.6)
- vserver patch (ctx) 1:1.29-2
- util-vserver 0.30-8
- vserver-debiantools 0.1.4
I had created vservers under kernel 2.4.25: the only things I changed from
the "default" config were the name and IP address (no "capability" added or
removed).
Now I have to run kernel 2.6.
Unfortunetaly, there are errors now; the following is the output from the console:
---START-TRANSCRIPT---
# vserver golem start
Starting the virtual server golem
Error: /proc must be mounted
To mount /proc at boot you need an /etc/fstab line like:
/proc /proc proc defaults
In the meantime, mount /proc /proc -t proc
Server golem is not running
ipv4root is now 192.168.83.10
Host name is now golem
New security context is 49154
Starting system log daemon: syslogd.
Starting MTA: exim4.
Starting OpenBSD Secure Shell server: sshd.
Starting internet superserver: xinetd.
Starting deferred execution scheduler: atd.
Starting periodic command scheduler: cron.
dawn:/home/eran# ping golem
PING golem.harfang.homelinux.org (192.168.83.10) 56(84) bytes of data.
64 bytes from golem.harfang.homelinux.org (192.168.83.10): icmp_seq=1 ttl=64 time=0.070 ms
64 bytes from golem.harfang.homelinux.org (192.168.83.10): icmp_seq=2 ttl=64 time=0.067 ms
64 bytes from golem.harfang.homelinux.org (192.168.83.10): icmp_seq=3 ttl=64 time=0.068 ms
--- golem.harfang.homelinux.org ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1999ms
rtt min/avg/max/mdev = 0.067/0.068/0.070/0.006 ms
# vserver golem enter
Error: /proc must be mounted
To mount /proc at boot you need an /etc/fstab line like:
/proc /proc proc defaults
In the meantime, mount /proc /proc -t proc
ipv4root is now 192.168.83.10
Can't set the host name (Operation not permitted)
New security context is 49154
golem:/# ifconfig
Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
golem:/# ping dawn
PING dawn.harfang.homelinux.org (192.168.107.10) 56(84) bytes of data.
[Ctrl-C]
--- dawn.harfang.homelinux.org ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms
golem:/# exit
# vserver golem stop
Stopping the virtual server golem
Error: /proc must be mounted
To mount /proc at boot you need an /etc/fstab line like:
/proc /proc proc defaults
In the meantime, mount /proc /proc -t proc
Server golem is not running
---END-TRANSCRIPT---
(1) [dawn is the name of the host].
Pinging the host was working when in 2.4.25.
(2) When stopping, it said "Server golem is not running". How could I ping the
vserver then?
(3) About "/proc must be mounted", the following is from the vserver directory:
---START-FSTAB---
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
---END-FSTAB---
(4) Some problems seem related to the specific kernel version:
My "/etc/network/insterfaces" file contains:
---START-INTERFACES---
auto dummy0
iface dummy0 inet static
address 192.168.83.1
netmask 255.255.255.0
broadcast 192.168.83.255
auto dummy1
iface dummy1 inet static
address 192.168.79.1
netmask 255.255.255.0
broadcast 192.168.79.255
---END-INTERFACES---
"ifup dummy0" works fine but "ifup dummy1" doesn't, showing the following
errors:
---START-IFUP---
SIOCSIFADDR: No such device
dummy1: ERROR while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
dummy1: ERROR while getting interface flags: No such device
dummy1: ERROR while getting interface flags: No such device
Failed to bring up dummy1.
---END-IFUP---
I want to switch to a more recent kernel, but there is no Debian follow-up for
the "ctx" patch. :-{ The Debian-provided patch is meant for kernel 2.6.6 only.
Is there some reason for this?
Should I make a new kernel from the "vanilla" source, thus ceasing to use the
kernel-package tools?
> 1. Debian sarge/testing kernel 2.6.8
> 2. Patch vserver 1.9.3rc2
> 3. Compile + install util-vserver-0.30.195
> 4. Verify and/or install deb "debootstrap" with the version
> corresponding with same sarge/testing CD1 used ( for my case:
> debootstrap 0.2.39.1 with sarge : first of August 2004 )
> 5. mount CD1 from SARGE on /cdrom
> 6. create /etc/vservers/.defaults/apps/debootstrap/mirror (->
> file:/cdrom )
> 5. "vserver vm1 build -m debootstrap -- -d sarge"
> 6. Configuration by creating files in the new file config tree:
> /etc/vservers/vm1/flags ( -> hide_mount )
> /etc/vservers/vm1/name (-> vm1 )
> /etc/vservers/vm1/interfaces/00/dev ( -> eth0 )
> /etc/vservers/vm1/interfaces/00/ip ( -> xx.xx.xx.xx )
> /etc/vservers/vm1/interfaces/00/mask ( -> yy.yy.yy.yy )
> /etc/vservers/vm1/apps/init/runlevel ( -> 2 )
> /etc/vservers/vm1/uts/nodename (-> vm1 )
>
> Hope this details will help anyone who wants to have a good solution
> with kernel 2.6.
That should help, but couldn't some of it be more automated using
"newvserver" or "dupvserver" from the vserver-debiantools package?
Also, I don't have the directories you indicate in step 6.
Thanks for your advices.
Gilles
_______________________________________________
Vserver mailing list
Vserver_at_list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver