could not start container

[screenie]

i have setup a pve cluster with the version: pve-manager/1.4/4390

yesterdy i created an kvm host and it works, now i created an openvz host (template debian-5.0-standard_5.0-1_i386.tar.gz) but cannot start it;
i get these entries in /var/log/syslog:

Oct 23 21:23:49 vServer01 pvedaemon[20640]: starting VM 102 on node 1 (localhost)
Oct 23 21:23:49 vServer01 proxwww[20648]: Starting new child 20648
Oct 23 21:23:49 vServer01 kernel: [90594.998229] CT: 102: started
Oct 23 21:23:50 vServer01 kernel: [90595.698513] device veth102.0 entered promiscuous mode
Oct 23 21:23:50 vServer01 kernel: [90595.705635] vmbr6: port 3(veth102.0) entering learning state
Oct 23 21:23:50 vServer01 kernel: [90595.717633] vmbr6: topology change detected, propagating
Oct 23 21:23:50 vServer01 kernel: [90595.720000] vmbr6: port 3(veth102.0) entering forwarding state
Oct 23 21:23:50 vServer01 pvedaemon[20640]: VM 102 started
Oct 23 21:23:50 vServer01 kernel: [90595.754506] vmbr6: port 3(veth102.0) entering disabled state
Oct 23 21:23:50 vServer01 kernel: [90595.828798] device veth102.0 left promiscuous mode
Oct 23 21:23:50 vServer01 kernel: [90595.835078] vmbr6: port 3(veth102.0) entering disabled state
Oct 23 21:23:50 vServer01 kernel: [90596.009511] CT: 102: stopped


any ideas?

 

[dietmar]

What do you get when you start it manually:

# vzctl start 102

 

[screenie]

pebox1:/# vzctl start 103
Starting container ...
Container is unmounted
Container is mounted
[79269.172111] CT: 103: started
Setting CPU units: 1000
Setting CPUs: 1
Configure meminfo: 262144
Set hostname: test.domain.local
File resolv.conf was modified
Setting quota ugidlimit: 0
Configure veth devices: veth103.0
Adding interface veth103.0 to br[79269.300109] device veth103.0 entered promiscuous mode
idge vmbr6 on CT[79269.302831] vmbr6: port 3(veth103.0) entering learning state
0 for CT103
[79269.312460] vmbr6: topology change detected, propagating
[79269.322218] vmbr6: port 3(veth103.0) entering forwarding state
Container start in progress...
pebox1:/# [79269.347895] vmbr6: port 3(veth103.0) entering disabled state
[79269.394630] device veth103.0 left promiscuous mode
[79269.400014] vmbr6: port 3(veth103.0) entering disabled state
[79269.584787] CT: 103: stopped

pebox1:/#

 

[screenie]

is there a way for a more detailed troubleshooting?

i am runninig pve on a standard debian lenny instead the bare metal version because it is an 1he server and hardware raid is not possible, so md-devices are a must to have;

maybe there is something different on the bare metal pve version to the standard debian lenny installation? (except the kernel)

thx

 

[screenie]

i tried an another machine the baremetal installer and it works;
then on the same hardware with debian lenny and pve and it don't work....

looks like there is something different from the baremetal to the standard debian...

 

[screenie]

found the problem - vzctl 3.0.23-1pve3 does not work with the debian standard kernel;

using the vzctl from the standard debian repository and it works....

 

[dietmar]

found the problem - vzctl 3.0.23-1pve3 does not work with the debian standard kernel;

Any idea why it does not work?

 

[screenie]

hummm......i am not sure.....

in the vzctl from the debian repository, you cannot specify the bridge interface within the --netif_add option, so vlan's with additional bridge interfaces are not usable....

maybe this is also the problem that the openvz code in the debian standard kernel does not know the bridge parameter from the --netif_add option or the newer vzctl version from the pve repository is not 100% combatible with the openvz kernel from debian lenny?
because trying to set the interface gives the following error:
'Error: unable to apply VM settings, command failed: /usr/bin/pvectl vzset 102 --netif ifname=eth0,bridge=vmbr1,mac=BA:33:22:11:00:AA,host_mac=BE:18:51:30:5F:9A'
and the script /usr/bin/pvectl calls vzctl

debian lenny vzctl version 3.0.22:
[--netif_add <ifname[,mac,host_ifname,host_mac]]>] [--netif_del <ifname>]

pve vzctl version 3.0.23-1pve3:
[--netif_add <ifname[,mac,host_ifname,host_mac,bridge]]>] [--netif_del <ifname>]

i did also an 'strace vzctl start 102' with both versions of vzctl - but i did not see something;

the ve only runs with the vzctl from the debian repository and only from commandline, because starting the ve from the pve-gui set's the bridge parameter which the vzctl version dont understand;