About this list Date view Thread view Subject view Author view Attachment view

From: [eMAXX] Sys-Admin (sys-admin_at_emaxx.nl)
Date: Tue 13 Sep 2005 - 21:32:30 BST


Hi folks,

Ok, I'm totally lost. I don't seem to get a vserver install to work...
well at least not the latest version..

I'm trying to install vserver from this source:
http://linux-vserver.derjohn.de/ on Debian Sarge. I written down the
steps I took for this vserver installation:

-----
Vserver 2.0 Installation on Debian Sarge current running 2.6.8 kernel

Used info:
- http://linux-vserver.org/Step-by-Step+Guide+2.6

Used sources:
- http://linux-vserver.derjohn.de/
- http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh

------------------------------------------------------
[1] Wget:
    
http://linux-vserver.derjohn.de/kernel-image-2.6.12-p3_10.00.vserver20_i386.deb
    http://linux-vserver.derjohn.de/util-vserver_0.30.208-1_i386.deb
   
[2] Install new kernel:
    ~# dpkg -i kernel-image-2.6.12-p3_10.00.vserver20_i386.deb
   
[2a] Update /boot/grub/menu.lst to change the label so it contains "vs"
    ~# nano /boot/grub/menu.lst
   
[3] Reboot...

---

[4] Install Util-Vserver: ~# dpkg -i util-vserver_0.30.208-1_i386.deb [5] download and run the testscript: ~# wget http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh

~# chmod +x testme.sh ~# ./testme.sh

Output of the test script:: Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl chcontext is working. chbind is working. Linux 2.6.12-p3 i686/0.30.208/0.30.208 [Ea] (0) VCI: 0002:0001 273 03000076 --- [000]# succeeded. [001]# succeeded. [011]# succeeded. [031]# succeeded. [101]# succeeded. [102]# succeeded. [201]# succeeded. [202]# succeeded.

[6] So, vserver 2.0 and vserver-util should be running now: ~# vserver-info Versions: Kernel: 2.6.12-p3 VS-API: 0x00020001 util-vserver: 0.30.208; Aug 12 2005, 01:59:02 Features: CC: i486-linux-gnu-gcc, i486-linux-gnu-gcc (GCC) 4.0.2 20050725 (prerelease) (Debian 4.0.1-3) CXX: i486-linux-gnu-g++, i486-linux-gnu-g++ (GCC) 4.0.2 20050725 (prerelease) (Debian 4.0.1-3) CPPFLAGS: '' CFLAGS: '-Wall -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: i486-pc-linux-gnu/i486-pc-linux-gnu Use dietlibc: yes Build C++ programs: yes Build C99 programs: yes Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts ext2fs Source: e2fsprogs syscall(2) invocation: alternative vserver(2) syscall#: 273/glibc Paths: prefix: /usr sysconf-Directory: ${prefix}/etc cfg-Directory: ${prefix}/etc/vservers initrd-Directory: $(sysconfdir)/init.d pkgstate-Directory: ${prefix}/var/run/vservers Kernelheaders: /lib/modules/2.6.11.john-win4lin-1-ath64/build/include vserver-Rootdir: /vservers

---

[7] Create Vserver basedir since the default location isn't there: ~# mkdir /vservers ~# mkdir /vservers/vstest01

[8] Create new Context/Virtual Server: ~# vserver vstest01 build -m debootstrap --hostname vstest01 --netdev eth0:vs01 --interface 192.168.27.33 --context 42 -- -d sarge -m ftp://ftp.nl.debian.org/debian/ [9] /proc/sys/kernel/vshelper contains: /sbin/vshelper, must be updated: ~# echo "/usr/lib/util-vserver/vshelper" >/proc/sys/kernel/vshelper [10] Then Vserver should run? ~# vserver vstest01 start /proc/uptime can not be accessed. Usually, this is caused by procfs-security. Please read the FAQ for more details http://www.linux-vserver.org/index.php?page=Linux-Vserver+FAQ

----

I search the irc-log and then tried this: ~# /usr/lib/util-vserver/vprocunhide /proc/net/: Bad address /proc/sys/: Bad address /proc/sys/debug/: Bad address /proc/sys/dev/: Bad address /proc/sysvipc/: Bad address /proc/tty/: Bad address /proc/cmdline: Bad address /proc/cpuinfo: Bad address /proc/crypto: Bad address /proc/devices: Bad address /proc/execdomains: Bad address /proc/filesystems: Bad address /proc/interrupts: Bad address /proc/iomem: Bad address /proc/ioports: Bad address /proc/kcore: Bad address /proc/kmsg: Bad address /proc/loadavg: Bad address /proc/locks: Bad address /proc/meminfo: Bad address /proc/misc: Bad address /proc/modules: Bad address /proc/pci: Bad address /proc/slabinfo: Bad address /proc/stat: Bad address /proc/swaps: Bad address /proc/uptime: Bad address /proc/version: Bad address

I have no clue what this means.... anyone?

Regards,

Vincent Pluk eMAXX, Netherlands _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver


About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Tue 13 Sep 2005 - 21:30:53 BST by hypermail 2.1.3