OpenVZ container to new host

[cutty]

Hi,

I have been moving guests (both OpenVZ & KVM) to a new Proxmox VE Host.
Old host was V1.8, new host is V1.9.
I have a problem with one OpenVZ container (piaf). I can do vzrestore and start it ok and the applications inside the guest work.
The problem is that I cannot SSH (or console VNC) successfully. I can connect but there is no OS prompt.
From the host, vzctl enter 107 returns "entered into 107" but still no prompt.
I did a vzrestore as a different VMID to the original host and it works as it should.
I assume the problem must be with the new V1.9 machine.

Any ideas?

 

[dietmar]

Any hint in the init.log?

 

[svenr]

Maybe /dev/null is corrupt. I had similar issues and solved them with recreating /dev/null bevor starting the vm.

sven

 

[dca]

i have the same issues with piaf
template=centos-5.5-purple1.8.2.1-piaf_1.7.5.5.4-1_amd64


pveversion for the 1.8 system
pve-manager: 1.8-17 (pve-manager/1.8/5948)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-33
pve-kernel-2.6.32-4-pve: 2.6.32-33
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.26-1pve4
vzdump: 1.2-12
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-3
ksm-control-daemon: 1.0-5

View attachment 1.8_init.log.txt

for the 1.9 system ( updated today feb 8 )
pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55+ovzfix-1
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1
qemu-server: 1.1-32
pve-firmware: 1.0-14
libpve-storage-perl: 1.0-19
vncterm: 0.9-2
vzctl: 3.0.29-3pve1
vzdump: 1.2-16
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.15.0-2
ksm-control-daemon: 1.0-6

View attachment 1.9_init.log.txt


also tryed downloading new templete from http://proxmox.pbxinaflash.com/ PIAF 1.7.5-5 Purple 1.8.6.0 - OpenVZ (CentOS 5.7-64 bit) and it will not start correctly in 1.9 ether

thanks for any help

 

[bobdobelina]

I believe piaf is not compatible with the kernel in 1.9 version, works in 1.8 running

2.6.32-4-pve​

 

[cutty]

I have been away for a while but started mucking around with this problem today.
I found that the root login profile ".bash_profile" runs the "/usr/local/sbin/status" file.
I just renamed "status" to "status1" and I'm able to get the prompt (with a command not found error).
All it means is you don't get the piaf status screen when you log in via ssh.
Further fault finding was time consuming with no result and I decided I don't need that status screen anyway.
So now I will just edit the bash profile so it doesn't run the status command.