No, I don't see anything at all in dmesg. Looking though the files in the log directory, I can see the eth* devices startup. Followed by venet0. But I don't see any errors until the point that the vz init script tries to bring up the VE that is set to auto start. Then it show the same error I get interactively.
Jul 13 23:26:37 nd1 kernel: ip_conntrack version 2.4 (8192 buckets, 65536 max) - 288 bytes per conntrack
Jul 13 23:26:38 nd1 kernel: VE: 29: started
Jul 13 23:26:38 nd1 kernel: VE: 29: stopped
Jul 13 23:26:39 nd1 vz: Starting VE ... VE is mounted Setting CPU units: 24554 Configure meminfo: 308092
Set hostname: dev2.xxxxx.com File resolv.conf was modified Configure veth devices: veth29.0 vet
h29.1 Error: veth feature is not supported by kernel VE start failed Stopping VE ... VE was stopped VE
is unmounted failed
OpenVZ Forum
Members
Search
Help
Register
Login
Home
