Home » General » Support » *SOLVED* veth problem - unable to create
*SOLVED* veth problem - unable to create [message #10938] |
Wed, 07 March 2007 23:35 |
gramsa49
Messages: 17 Registered: February 2007
|
Junior Member |
|
|
Not sure what I am doing wrong here. I added the veth device, but after I restarted, it was gone; now I can not add it back. Any guidance would be greatly appreciated.
I added the veth device using this command:
vzctl set 2040 --netif_add veth101.0,xx:xx:xx:xx:xx:xx,eth0,yy:yy:yy:yy:yy:yy --save
<result of trying to add the device to veid 2040 from host>
[root@vz1 ~]# vzctl set 2040 --netif_add veth0,xx:xx:xx:xx:xx:xx,eth0,xx:xx:xx:xx:xx:yy --save
Configure veth devices: eth0
Unable to create veth: File exists
Saved parameters for VE 2040
<list of interfaces on host machine>
[root@vz1 ~]# ifconfig -a
bond0 Link encap:Ethernet HWaddr 00:08:02:25:2E:F3
inet addr:10.1.1.110 Bcast:10.1.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
RX packets:2821 errors:0 dropped:0 overruns:0 frame:0
TX packets:6461 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:699356 (682.9 KiB) TX bytes:1031319 (1007.1 KiB)
eth0 Link encap:Ethernet HWaddr 00:08:02:25:2E:F3
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:2765 errors:0 dropped:0 overruns:0 frame:0
TX packets:2980 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:693641 (677.3 KiB) TX bytes:318665 (311.1 KiB)
eth1 Link encap:Ethernet HWaddr 00:08:02:25:2E:F2
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
RX packets:56 errors:0 dropped:0 overruns:0 frame:0
TX packets:3481 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5715 (5.5 KiB) TX bytes:712654 (695.9 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:304 (304.0 b) TX bytes:304 (304.0 b)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:1702 errors:0 dropped:0 overruns:0 frame:0
TX packets:1542 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:587534 (573.7 KiB) TX bytes:574299 (560.8 KiB)
<interfaces on veid 2040>
[root@vz1 ~]# vzctl enter 2040
entered into VE 2040
[root@arsdev /]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1230259009 errors:0 dropped:0 overruns:0 frame:0
TX packets:1631407695 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1140876388 (1.0 GiB) TX bytes:1095784005 (1.0 GiB)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Before someone asks, here are the results of checking for the kernel modules required for veth:
[root@vz1 ~]# lsmod | grep vzeth
vzethdev 8008 0
vzmon 49132 9 vzethdev,vzrst,vzcpt,vznetdev
vzdev 2208 4 vzethdev,vzdquota,vznetdev,vzmon
Here is my kernel/software info; this is a multi-cpu machine. The test kernel is there because I was using it to test another issue; I do not use it for day to day operation.
[root@vz1 ~]# rpm -qa |grep vz
ovzkernel-smp-2.6.9-023stab040.1
vzrpm44-4.4.1-22.5
vzrpm43-python-4.3.3-7_nonptl.6
vztmpl-fedora-core-5-2.0-2
kernel-smp-2.6.18-ovz028test015.1
vzctl-lib-3.0.14-1
vzctl-3.0.14-1
vzyum-2.4.0-11
vzpkg-2.7.0-18
vzrpm43-4.3.3-7_nonptl.6
vzquota-3.0.9-1
vzrpm44-python-4.4.1-22.5
vztmpl-centos-4-2.0-2
[root@vz1 ~]# uname -a
Linux vz1.home.arswiki.org 2.6.9-023stab040.1-smp #1 SMP Tue Jan 16 00:54:22 MSK 2007 i686 i686 i386 GNU/Linux
What I've tried so far:
- restart ve
- restart host
- manually bring up veth interface:
[root@vz1 ~]# ifconfig veth101.0 up
veth101.0: unknown interface: No such device
Research
I did an strace for file operations to see what 'file' already exists.
[root@vz1 ~]# strace -s 10000 -e trace=file vzctl set 2040 --netif_add veth0,00:0B:CD:1E:5D:FA,eth0,00:0B:CD:1E:5D:FB --save
execve("/usr/sbin/vzctl", ["vzctl", "set", "2040", "--netif_add", "veth0,00:0B:CD:1E:5D:FA,eth0,00:0B:CD:1E:5D:FB", "--save"], [/* 20 vars */]) = 0
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib/tls/i686/libvzctl-0.0.2.so", O_RDONLY) = -1 ENOENT (No such file or directory)
stat64("/lib/tls/i686", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/lib/tls/libvzctl-0.0.2.so", O_RDONLY) = -1 ENOENT (No such file or directory)
stat64("/lib/tls", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/lib/i686/libvzctl-0.0.2.so", O_RDONLY) = -1 ENOENT (No such file or directory)
stat64("/lib/i686", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/lib/libvzctl-0.0.2.so", O_RDONLY) = -1 ENOENT (No such file or directory)
stat64("/lib", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/lib/tls/i686/libvzctl-0.0.2.so", O_RDONLY) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/tls/i686", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/lib/tls/libvzctl-0.0.2.so", O_RDONLY) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/tls", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/usr/lib/i686/libvzctl-0.0.2.so", O_RDONLY) = -1 ENOENT (No such file or directory)
stat64("/usr/lib/i686", 0xbfec1040) = -1 ENOENT (No such file or directory)
open("/usr/lib/libvzctl-0.0.2.so", O_RDONLY) = 3
open("/lib/libdl.so.2", O_RDONLY) = 3
open("/lib/libutil.so.1", O_RDONLY) = 3
open("/lib/tls/libc.so.6", O_RDONLY) = 3
open("/usr/lib/vzctl/modules/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOENT (No such file or directory)
open("/etc/vz/vz.conf", O_RDONLY) = 3
stat64("/etc/vz/vz.conf", {st_mode=S_IFREG|0644, st_size=709, ...}) = 0
open("/var/log/vzctl.log", O_WRONLY|O_APPEND|O_CREAT, 0666) = 3
stat64("/etc/vz/conf/2040.conf", {st_mode=S_IFREG|0644, st_size=1812, ...}) = 0
open("/etc/vz/conf/2040.conf", O_RDONLY) = 4
stat64("/etc/vz/conf/2040.conf", {st_mode=S_IFREG|0644, st_size=1812, ...}) = 0
open("/dev/vzctl", O_RDWR) = 4
stat64("/vz/lock", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
open("/vz/lock/2040.lck0NL00N", O_RDWR|O_CREAT|O_EXCL, 0600) = 5
link("/vz/lock/2040.lck0NL00N", "/vz/lock/2040.lck") = 0
unlink("/vz/lock/2040.lck0NL00N") = 0
open("/proc/vz/veth", O_RDONLY) = 5
Configure veth devices: eth0
open("/etc/localtime", O_RDONLY) = 5
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
Unable to create veth: File exists
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
stat64("/etc/vz/conf/2040.conf", {st_mode=S_IFREG|0644, st_size=1812, ...}) = 0
open("/etc/vz/conf/2040.conf", O_RDONLY) = 5
Saved parameters for VE 2040
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=1267, ...}) = 0
unlink("/vz/lock/2040.lck") = 0
Process 16642 detached
This was the only thing that sticks out, but not sure what I can/can't do with it.
[root@vz1 ~]# cat /proc/vz/veth
Version: 1.0
[Updated on: Fri, 09 March 2007 09:31] by Moderator Report message to a moderator
|
|
|
|
Goto Forum:
Current Time: Fri Oct 18 03:48:27 GMT 2024
Total time taken to generate the page: 0.05117 seconds
|