Centos 5.3 OpenVZ container not working after upgrade to Promox 1.9

[vkimball]

I just upgraded my Proxmox 1.8 server to 1.9 and now one of my OpenVZ containers doesn't boot.

Here is the output of pveversion:

proxmox1:~# pveversion -v
pve-manager: 1.9-24 (pve-manager/1.9/6542)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-47
pve-kernel-2.6.32-4-pve: 2.6.32-33
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.32-6-pve: 2.6.32-47
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-2pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-1
ksm-control-daemon: 1.0-6

and here is the boot log from the VM:

INIT: version 2.86 booting
Welcome to CentOS release 5.3 (Final)
Press 'I' to enter interactive startup.
hwclock is unable to get I/O port access: the iopl(3) call failed.
Setting clock (localtime): Sun Oct 2 21:07:54 CEST 2011 [ OK ]
Loading default keymap (us): /etc/rc.d/rc.sysinit: line 396: /dev/tty0: No such file or directory [FAILED]
Setting hostname vpbx.vincekimball.com: [ OK ]
raidautorun: failed to open /dev/md0: Operation not permitted
awk: cmd. line:1: fatal: cannot open file `/proc/misc' for reading (No such file or directory)
Mounting local filesystems: [ OK ]
Enabling local filesystem quotas: [ OK ]
/etc/rc.d/rc.sysinit: line 793: /dev/urandom: Operation not permitted
ng /etc/fstab swaps: [ OK ]
INIT: Entering runlevel: 3
Entering interactive startup<br>
Start service lvm2-monitor (Y)es/(N)o/(C)ontinue? [Y]

The VNC console doesn't let me see anything. Any ideas on how best to troubleshoot?

I have another OpenVZ VM and a KVM VM working normally.

Thanks in advance!
-- Vince

 

[eswood]

* Post removed *

My apologies. I had originally posted that I had the same symptoms as the OP but have since found the logs I posted were from a previous boot. I found the cause of my failed start in my /var/log/vzctl.log and it was unrelated to the 1.9 upgrade.

 

[vkimball]

Switching back to the 2.6.32-4-pve kernel seems to fix the problem.

 

[jvalla]

I have the same issue as OP. Can somebody please tell me how to fix it?

 

[vkimball]

Apparently no one has any idea? I can't upgrade past 2.6.32-4-pve because the VM doesn't boot.

 

[vkimball]

I'm happy to report that upgrading to the 2.6.32-7-pve kernel and increasing the number of cores assigned to the VM resolved the issue.