OpenVZ Forum: Support » *BUG* *SOLVED* vzctl-3.0.18 package breaks my veth devices

Home » General » Support » *BUG* *SOLVED* vzctl-3.0.18 package breaks my veth devices

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

*BUG* *SOLVED* vzctl-3.0.18 package breaks my veth devices [message #14942]

Fri, 13 July 2007 19:56

jb619
Messages: 6
Registered: June 2007

Junior Member

I upgraded my centos 4 HN to the latest vzctl package (vzctl-3.0.18) today. After rebooting, vzctl refuses to start VE's using veth devices. It complains that the feature is not supported by the kernel. If I downgrade to 3.0.16-1 and then reboot. Everything is back to normal.

[root@nd1 packages]# vzctl start 29
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 veth29.1
Error: veth feature is not supported by kernel
VE start failed
Stopping VE ...
VE was stopped
VE is unmounted

[root@nd1 packages]# uname -r
2.6.18-ovz028stab035.1-smp

[root@nd1 packages]# rpm -Uvh --oldpackage vzctl-3.0.16-1.x86_64.rpm vzctl-lib-3.0.16-1.x86_64.rpm
Preparing...                ########################################### [100%]
   1:vzctl-lib              ########################################### [ 50%]
   2:vzctl                  ########################################### [100%]

[root@nd1 packages]# vzctl start 29
Starting VE ...
VE is mounted
Setting CPU units: 24554
Set hostname: dev2.careerperfect.com
File resolv.conf was modified
Configure veth devices: veth29.0 veth29.1
Error: veth feature is not supported by kernel
VE start failed
Stopping VE ...
VE was stopped
VE is unmounted

[root@nd1 packages]# init 6


$ ssh root@nd1.XXXX.com

[root@nd1 ~]# vzlist
      VEID      NPROC STATUS  IP_ADDR         HOSTNAME
        29         28 running                 dev2.XXXX.com

I am not sure where to even start on troubleshooting this. Has anyone seen anything like it or have some ideas?

--John

[Updated on: Mon, 16 July 2007 11:04] by Moderator

Report message to a moderator

Re: vzctl-3.0.18 package breaks my veth devices [message #14943 is a reply to message #14942]

Fri, 13 July 2007 20:06

curx
Messages: 739
Registered: February 2006
Location: Nürnberg, Germany

Senior Member

Hi John,

is the kernel modul "vzethernet" loaded in your VE0 (hardwarenode) ?

Report message to a moderator

Re: vzctl-3.0.18 package breaks my veth devices [message #14944 is a reply to message #14943]

Fri, 13 July 2007 20:25

jb619
Messages: 6
Registered: June 2007

Junior Member

No, it is not present. Did you mean "vzethdev"?

--John

Report message to a moderator

Re: vzctl-3.0.18 package breaks my veth devices [message #14945 is a reply to message #14942]

Fri, 13 July 2007 20:44

jb619
Messages: 6
Registered: June 2007

Junior Member

It looks like when vzctl 3.0.18 is installed vzethdev is not getting loaded.

This is with 3.0.16:

[root@nd1 packages]# lsmod|grep vze
vzethdev               10768  0
vzmon                  35216  5 vzethdev,vzrst,vzcpt,vznetdev
vzdev                   4360  4 vzethdev,vzdquota,vznetdev,vzmon


[root@nd1 packages]# rpm -Uvh vzctl-3.0.18-1.x86_64.rpm vzctl-lib-3.0.18-1.x86_64.rpm
Preparing...                ########################################### [100%]
   1:vzctl-lib              ########################################### [ 50%]
   2:vzctl                  ########################################### [100%]
[root@nd1 packages]# init 6
[root@nd1 packages]# exit

Then after the upgrade to 3.0.18 and a reboot:


johnb@booboo:~$ ssh root@nd1.xxxx.com

[root@nd1 ~]# lsmod|grep vze
[root@nd1 ~]# 

[root@nd1 ~]# vzctl start 29
Starting VE ...
VE is mounted
Setting CPU units: 24554
Configure meminfo: 308092
Set hostname: dev2.xxxx.com
File resolv.conf was modified
Configure veth devices: veth29.0 veth29.1
Error: veth feature is not supported by kernel
VE start failed
Stopping VE ...
VE was stopped
VE is unmounted


[root@nd1 ~]# modprobe vzethdev

[root@nd1 ~]# vzctl start 29
Starting VE ...
VE is mounted
Setting CPU units: 24554
Configure meminfo: 308092
Set hostname: dev2.xxxx.com
File resolv.conf was modified
Configure veth devices: veth29.0 veth29.1
VE start in progress...

I will take a look at /etc/init.d/vz and see if I can figure out why the module is not being loaded.

--John

Report message to a moderator

Re: vzctl-3.0.18 package breaks my veth devices [message #14946 is a reply to message #14942]

Fri, 13 July 2007 22:55

jb619
Messages: 6
Registered: June 2007

Junior Member

The problem is in the new version of the /etc/init.d/vz script included with 3.0.18. In the new version, vzethdev is moved out of MODULES_OTHER and moved into NET_MODULES. This is the trigger. If I manually edit the init script and move vethdev back into MODULES_OTHER, the problem goes away.

I am not sure why this change is causing a problem on my system. Since MODULES_OTHER are loaded before NET_MODULES, the change causes vzethdev to be loaded slightly latter in the process. Also, this only effects the first vz startup after a reboot. If after a reboot where vzethdev does not load, I then use the init script to stop and then start vz, the module loads. It seems to be some sort of timing / dependency issue, but I am not familiar enough with the details of openvz startup to guess where it is.

--John

Report message to a moderator

Re: vzctl-3.0.18 package breaks my veth devices [message #14950 is a reply to message #14946]

Sat, 14 July 2007 03:06

kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia

Senior Member

is there anything in dmesg that tells why vzethdev is not loaded?

Kir Kolyshkin

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: vzctl-3.0.18 package breaks my veth devices [message #14954 is a reply to message #14942]

Sat, 14 July 2007 05:23

jb619
Messages: 6
Registered: June 2007

Junior Member

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

Report message to a moderator

Re: vzctl-3.0.18 package breaks my veth devices [message #14998 is a reply to message #14942]

Mon, 16 July 2007 11:03

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

In the patch http://git.openvz.org/?p=vzctl;a=commitdiff;h=f09fd723bbe70d 98b772bd9d13fdf844d14cad59 vzethdev is moved from MODULES_OTHER to NET_MODULES and this caused the problem:

if ip addr list | grep -q "venet0:.*UP"; then
    return 0
fi

triggers, but vzethdev is not loaded...

The attached patch forces to try to load kernel modules at the beginning of VE networking start.

Just apply this patch to /etc/init.d/vz

Thanks for the report,
Vasily

Attachment: diff-vz-veth-module-on-hn-start-20070716
(Size: 0.53KB, Downloaded 287 times)

Report message to a moderator

Re: *BUG* *SOLVED* vzctl-3.0.18 package breaks my veth devices [message #15010 is a reply to message #14942]

Mon, 16 July 2007 17:34

jb619
Messages: 6
Registered: June 2007

Junior Member

I applied the patch to the vz init script from 3.0.18 and rebooted. When I reconnected, vzethdev was loaded and my VE's had started up. So I can confirm that the patch fixes the issue.

Thanks for everyone's help.

--John

Report message to a moderator