bridge connection

R

RRJ

Member
Apr 14, 2010
245
0
16
Estonia, Tallinn
after upgrade to 1.6 i cannot setup vmbr connection any more :(

web interface says that command failed on saving the parameters. and the existing connection doesnt work on vmbr :(
 
more info about your setup?
 
if i try to run the command from console (the one, that showed on web interface error) i receive this error:
VE 104 is not managed by PVE (origin sample is split5)
are You guys changed the way i can manage my pves? actually i cant change anything via the web interface any more :(
 
pls do not mix topics inside a thread, new issue, new thread please.
 
the issue is the same - i cant configure bridge connections. but as far as i understand this could be because of the changes. what should i do to get it working? :)
 
great. now i cant access my vms via web :)
[5224]ERR: 24: Error in Perl code: unable to get openvz vm list?
 
again: more info about your setup? otherwise no one can help.
 
okay, i've managed to get my web ui back on.
now, i understand, that since last update i cannot mix the vzctl set setup with pvectl, otherwise there is an error if i change something to the web config. ok. i re-created the config with ORIGIN_SAMPLE="pve.auto"
i can manage this pve via WEB now, but when i save the configuration for
Bridged Ethernet Devices
eth0: vmbr0
nothing happens and there are no changes in the conf file. so i cant even see the eth0 in pve. there is vmbr0 on the host.
what setup are You interested in?
this one?

CPUUNITS="1000"
CPUS="4"
VE_ROOT="/var/lib/vz/root/$VEID"
VE_PRIVATE="/var/lib/vz/private/$VEID"
OSTEMPLATE="ubuntu-10.04-server-amd64"
ORIGIN_SAMPLE="pve.auto"
HOSTNAME="mypve"
NAMESERVER="192.168.250.230"
SEARCHDOMAIN="my.local"

oh, and there is no veth104.0 created for the pve.
 
Last edited:
is there any hint in syslog? Something like:

Sep 3 13:35:51 oahu pvedaemon[2722]: ERROR: unable to parse config line: IP_ADDRESS="#012

just delete the IP_ADDRESS line from the config - then it should work again.

i will try to fix the bug asap.
 
ok, the bug is in new vzctl:

# vzctl set <vmid> --ipdel xxx

generates invalid config line. will try to fix that.
 
yes, i found this too. the line looks like IP=" :) one " is missed. but it is not as urgent as this:


Sep 3 14:54:39 sisemon kernel: Call Trace:
Sep 3 14:54:39 sisemon kernel: [<ffffffff8117b1d8>] ? kobject_add_internal+0x16e/0x181
Sep 3 14:54:39 sisemon kernel: [<ffffffff8117b397>] ? kobject_add+0x74/0x7c
Sep 3 14:54:39 sisemon kernel: [<ffffffff8117b273>] ? kobject_set_name_vargs+0x4e/0x56
Sep 3 14:54:39 sisemon kernel: [<ffffffff810e8a8c>] ? __kmalloc+0x15a/0x17f
Sep 3 14:54:39 sisemon kernel: [<ffffffff812ed4f6>] ? mutex_lock+0xd/0x31
Sep 3 14:54:39 sisemon kernel: [<ffffffff8117afff>] ? kobject_get+0x12/0x17
Sep 3 14:54:39 sisemon kernel: [<ffffffff8120dd9f>] ? get_device_parent_nodep+0x125/0x19f
Sep 3 14:54:39 sisemon kernel: [<ffffffff8120edbb>] ? device_add+0xce/0x53f
Sep 3 14:54:39 sisemon kernel: [<ffffffffa039639c>] ? veth_setup+0x9/0x3f [vzethdev]
Sep 3 14:54:39 sisemon kernel: [<ffffffff81242697>] ? register_netdevice+0x218/0x30c
Sep 3 14:54:39 sisemon kernel: [<ffffffff812427c4>] ? register_netdev+0x39/0x46
Sep 3 14:54:39 sisemon kernel: [<ffffffffa039633b>] ? veth_dev_start+0xa5/0xfd [vzethdev]
Sep 3 14:54:39 sisemon kernel: [<ffffffffa03969e4>] ? veth_entry_add+0x102/0x245 [vzethdev]
Sep 3 14:54:39 sisemon kernel: [<ffffffffa0396d7c>] ? real_ve_hwaddr+0xef/0x17f [vzethdev]
Sep 3 14:54:39 sisemon kernel: [<ffffffffa0396e7d>] ? veth_ioctl+0x71/0x90 [vzethdev]
Sep 3 14:54:39 sisemon kernel: [<ffffffffa03201cd>] ? vzctl_ioctl+0x39/0x54 [vzdev]
Sep 3 14:54:39 sisemon kernel: [<ffffffff810fc91a>] ? vfs_ioctl+0x21/0x6c
Sep 3 14:54:39 sisemon kernel: [<ffffffff810fce68>] ? do_vfs_ioctl+0x48d/0x4cb
Sep 3 14:54:39 sisemon kernel: [<ffffffff810f140e>] ? vfs_write+0xcd/0x102
Sep 3 14:54:39 sisemon kernel: [<ffffffff810fcee3>] ? sys_ioctl+0x3d/0x5c
Sep 3 14:54:39 sisemon kernel: [<ffffffff81010c12>] ? system_call_fastpath+0x16/0x1b

when i try to add breged interface.
 
i've managed to get network working with venet device, i think there just some duplicated bridge config files left in the system, so it cannot create veth104:0 interface again due to some missconfiguration because i've messed up the vzctl and pvectl configs. if i knew where to find them, i'd deleted them. it was just a bit urgent to me to get network working on this pve, as i've got tacacs server running there :) now i've got some time to find the real bug, why the bridged interface doesnt work. any help is welcomed and i'll help from my side as i can to.
 
worked like a charm. now if i delete ip address the line in conf looks right
IP_ADDRESS=""

but what about vriged interfaces? :)
 
nope, it doesnt.
i think it is less related to proxmox as we can see from dmesg

Code: 
kobject_add_internal failed for eth0 with -EEXIST, don't try to register things with the same name in the same directory.
Pid: 27168, comm: vzctl Tainted: G        W  2.6.32-3-pve #1
Call Trace:
 [<ffffffff8117b1d8>] ? kobject_add_internal+0x16e/0x181
 [<ffffffff8117b397>] ? kobject_add+0x74/0x7c
 [<ffffffff8117b273>] ? kobject_set_name_vargs+0x4e/0x56
 [<ffffffff810e8a8c>] ? __kmalloc+0x15a/0x17f
 [<ffffffff812ed4f6>] ? mutex_lock+0xd/0x31
 [<ffffffff8117afff>] ? kobject_get+0x12/0x17
 [<ffffffff8120dd9f>] ? get_device_parent_nodep+0x125/0x19f
 [<ffffffff8120edbb>] ? device_add+0xce/0x53f
 [<ffffffffa039639c>] ? veth_setup+0x9/0x3f [vzethdev]
 [<ffffffff81242697>] ? register_netdevice+0x218/0x30c
 [<ffffffff812427c4>] ? register_netdev+0x39/0x46
 [<ffffffffa039633b>] ? veth_dev_start+0xa5/0xfd [vzethdev]
 [<ffffffffa03969e4>] ? veth_entry_add+0x102/0x245 [vzethdev]
 [<ffffffffa0396d7c>] ? real_ve_hwaddr+0xef/0x17f [vzethdev]
 [<ffffffffa0396e7d>] ? veth_ioctl+0x71/0x90 [vzethdev]
 [<ffffffffa03201cd>] ? vzctl_ioctl+0x39/0x54 [vzdev]
 [<ffffffff810fc91a>] ? vfs_ioctl+0x21/0x6c
 [<ffffffff810fce68>] ? do_vfs_ioctl+0x48d/0x4cb
 [<ffffffff810f140e>] ? vfs_write+0xcd/0x102
 [<ffffffff810fcee3>] ? sys_ioctl+0x3d/0x5c
 [<ffffffff81010c12>] ? system_call_fastpath+0x16/0x1b
eth0 initialization error err=-17
there is some info about interface with name veth104.0 already exists. but in some reason i cant get this iface up with ifconfig up veth104.0 nor ifup veth104.0 and cant add it in brctl:

Code: 
sisemon:~# brctl show
bridge name     bridge id               STP enabled     interfaces
vmbr0           8000.00237dfbc310       no              eth0
                                                        veth102.0
                                                        veth105.0

and

Code: 
sisemon:~# brctl addif vmbr0 veth104.0
interface veth104.0 does not exist!

i think i should recreate it somehow, but i didnt really work with brctl or bridge in linux :) any help is welcomed.
 
well, the way i came to this was:

1. removing old .conf file with bridge int configured.
2. adding default config without any network/hostname etc options
3. and after that i've tried to add the bridge interface via the proxmox WUI.
 
You must log in or register to reply here.
Top Bottom