[Users] Starting CentOS 5.x container... never fully init's

[Tim Nelson]

I recently converted some physical CentOS 5.x boxen to OpenVZ containers. I followed the guide from the OpenVZ Wiki [1].


When starting these new containers, I'm finding that init is fired off, but nothing else is. So, if I 'vzctl start 103', it shows the container is started, no problems:


virtbox1:~# vzctl start 103
Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 1
Set hostname: pxebox.internal
File resolv.conf was modified
Setting quota ugidlimit: 0
Configure veth devices: veth103.0
Adding interface veth103.0 to bridge vmbr0 on CT0 for CT103
Container start in progress...


However, none of the services or networking have come up. If I 'vzctl enter 103' and 'ps aux', here is the output:


virtbox1:~# vzctl enter 103
entered into CT 103
[root at pxebox /]# ps aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.0   2068   612 ?        Ss   20:42   0:00 init [3]
root        21  0.0  0.0    100    16 ?        S    20:42   0:00 [init-logger]
root       117  0.0  0.1   4652  1328 ?        Ss   20:42   0:00 /bin/bash /etc/rc.d/rc 3
root       121  0.0  0.0  18556   516 ?        Ss   20:43   0:00 vzctl: pts/0
root       122  0.1  0.1   4540  1384 pts/0    Ss   20:43   0:00 -bash
root       147  0.0  0.0   4256   924 pts/0    R+   20:43   0:00 ps aux


It appears init has fired off the appropriate rc runlevel 'rc 3' but it simply hangs. Nothing starts, no progress. If I then manually run rc.sysinit, then the rc 3 init, everything fires up with no problems:


[root at pxebox /]# /etc/rc.d/rc.sysinit
                Welcome to  CentOS release 5.4 (Final)
                Press 'I' to enter interactive startup.
hwclock is unable to get I/O port access:  the iopl(3) call failed.
Setting clock  (localtime): Thu Nov 18 20:45:57 CST 2010   [  OK  ]
Loading default keymap (us): /etc/rc.d/rc.sysinit: line 396: /dev/tty0: No such file or directory
                                                           [FAILED]
Setting hostname pxebox.fudnet:                            [  OK  ]
awk: cmd. line:1: fatal: cannot open file `/proc/misc' for reading (No such file or directory)
Checking filesystems
                                                           [  OK  ]
Mounting local filesystems:                                [  OK  ]
Enabling local filesystem quotas:                          [  OK  ]
/etc/rc.d/rc.sysinit: line 793: /dev/urandom: Operation not permitted
Enabling /etc/fstab swaps:                                 [  OK  ]

[root at pxebox /]# /etc/rc.d/rc 3
Applying Intel CPU microcode update: FATAL: Could not load /lib/modules/2.6.32-4-pve/modules.dep: No such file or directory
/etc/rc3.d/S00microcode_ctl: microcode device /dev/cpu/microcode doesn't exist?
Starting background readahead:                             [  OK  ]
Checking for hardware changes                              [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:                                [  OK  ]
Starting auditd:                                           [FAILED]
Starting system logger:                                    [  OK  ]
Starting kernel logger:                                    [  OK  ]
Starting irqbalance:                                       [  OK  ]
Starting system message bus:                               [  OK  ]
Mounting other filesystems:                                [  OK  ]
Starting HAL daemon:                                       [  OK  ]
Starting autofs:  Loading autofs4:                         [FAILED]
                                                           [FAILED]
Starting sshd:                                             [  OK  ]
Starting xinetd:                                           [  OK  ]
Starting vsftpd for vsftpd:                                [  OK  ]
Starting sendmail:                                         [  OK  ]
Starting sm-client:                                        [  OK  ]
Starting crond:                                            [  OK  ]
Starting anacron:                                          [  OK  ]
Starting atd:                                              [  OK  ]


Any ideas why this is happening? What is different about my interactive login to manually fire off the rc scripts versus the automated execution by init?

[1] http://wiki.openvz.org/Physical_to_container

--Tim