How to disable venet in a VE [message #33192] |
Sat, 27 September 2008 17:42  |
praveenray
Messages: 8 Registered: June 2008
|
Junior Member |
|
|
Hello
I've set up one of my VEs to use a veth. This VE was using venet earlier with an IP of 10.10.0.3. The new veth has the same IP. Now, since both veth and venet have the same IP, the networking doesn't work (it refuses to see any machine on the network). As soon as I do 'ifconfig venet0 down', everything works great.
I've trying to stop the venet from showing up in the VE with no success. This is in my $VEID.conf:
IP_ADDRESS=""
NETIF=" ifname=eth0,mac=00:18:51:96:29:24,host_ifname=veth219.0,host _mac=00:18:51:39:21:88 "
CONFIG_CUSTOMIZED="yes"
VETH_IP_ADDRESS="10.10.0.219/24"
VE_DEFAULT_GATEWAY="10.10.0.1"
BRIDGEDEV="br0"
I also have this in /etc/vz/vznet.conf:
EXTERNAL_SCRIPT="/usr/sbin/vznetcfg.custom"
and in vznetcfg.custom, towards the end, I do this:
$vzctl exec $VEID ifconfig venet0 down
$vzctl exec $VEID ifconfig venet0:0 down
However, a 'vzctl restart', gives this error(towards the end):
SIOCSIFFLAGS: Cannot assign requested address
However, the VE is alive at this point and if I do :
'vzctl exec 100 ifconfig venet0 down'
'vzctl exec 100 ifconfig venet0:0 down'
,all is well.
So, in short, how do I stop venet from appearing in my VE, if it is using veth?
Thanks
|
|
|
|
Re: How to disable venet in a VE [message #33201 is a reply to message #33198] |
Sun, 28 September 2008 02:10  |
praveenray
Messages: 8 Registered: June 2008
|
Junior Member |
|
|
yeah, I do not have 10.10.0.3 anywhere in the $VEID.conf file. I have following two lines:
IP_ADDRESS=""
VETH_IP_ADDRESS="10.10.0.219/24"
I was actually using 10.10.0.219..I mistyped it as 10.10.0.3 in my previous message. Sorry about the confusion - I've been trying too many things.
The bug you mentioned is exactly what I see so it's definitely my case.
Unloading vznetdev module works as expected but I could not find a way to do it at the boot time. I commented out this module in /etc/init.d/vz and even blacklisted this module but after doing /etc/init.d/vz restart, venet is still there and the module vznetdev somehow gets loaded anyway!
Very strange indeed!!
|
|
|