I created a Ubuntu 7.10 VE using the template from <http://openvz.org/download/template/cache>, but when I try to start it up I get the VE mounted but not accessible: # vzctl --version vzctl version 3.0.22-1dso1 # uname -a Linux vz 2.6.18-openvz-686 #1 SMP Tue Apr 10 20:28:40 CEST 2007 i686 GNU/Linux # vzctl --verbose start 1030 Starting VE ... VE is mounted Adding IP address(es): 192.168.10.30 Running VE script: /etc/vz/dists/scripts/debian-add_ip.sh Setting CPU units: 1000 Configure meminfo: 262144 Set hostname: ltsp.aldu.net Running VE script: /etc/vz/dists/scripts/debian-set_hostname.sh Running VE script: /etc/vz/dists/scripts/set_dns.sh File resolv.conf was modified VE start in progress... # vzlist -a ... 1030 - mounted 192.168.10.30 ltsp.aldu.net # vzctl enter 1030 VE is not running How can I see VE startup messages to find out what it's going wrong?
I've the same problem with a RHLE4 host. I can start an ubuntu 6.06 ve but not a ubuntu 7.10 and ubuntu 8.04 ve. I've similar entries in vzctl.log, and in messages I have following: Mar 26 20:24:48 whitestar kernel: VPS: 108: started Mar 26 20:24:50 whitestar kernel: VPS: 108: stopped # vzctl --version vzctl version 3.0.22 # uname -a Linux whitestar 2.6.9-023stab046.2 #1 Mon Dec 10 15:40:48 MSK 2007 x86_64 x86_64 x86_64 GNU/Linux PS: I did a reboot and tried it also there.
I've also a debian 4.0 host running, with following kernel and tools # uname -a Linux redstar 2.6.18-ovz-028stab048.1-smp #1 SMP Thu Nov 1 13:42:17 UTC 2007 x86_64 GNU/Linux # vzctl --version vzctl version 3.0.18-1dso1 on this system it works, but not on the rhel4 system above. Please help us to find the problem! thx.
Hi, I'm terribly sorry for delay. The reason is in the following: During the startup in /vz/private/VE_ID/etc/S35mountall.sh there is a such string: kill -USR1 1 From "man 2 kill" Quote: The only signals that can be sent task number one, the init process, are those for which init has explicitly installed signal handlers. This is done to assure the system is not brought down accidentally. This logic was broken down in old kernels. See http://bugzilla.openvz.org/show_bug.cgi?id=533 The problem was fixed in 2.6.18 kernels. There are several workarounds in your case: 1. If it is possible use the latest 2.6.18 kernel. 2. try to comment "kill -USR1 1" string in the script mentioned above. Thank You very much!
Thx, removing the "kill" line worked for me.
That worked form me too! Thanks
Wait... Commenting `kill -USR1 1' makes VE starting but no services inside VE are started: ubuntu-ve # ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 16:45 ? 00:00:00 init root 5815 1 0 16:45 ? 00:00:00 vzctl: pts/0 root 5819 5815 0 16:45 pts/0 00:00:00 -bash root 5857 5819 0 16:45 pts/0 00:00:00 ps -ef It's simply an unuseful VE My host's kernel: openvz-host # uname -r 2.6.18-openvz-686
works for me. have you installed any? the minial version has no services running as far es I know.
You're right, I just installed ubuntu-desktop and now I see many services!