I believe the xen scripts are rejiggering the network devices on startup, which is breaking them.b

(In reply to comment #0)
> Description of problem:
> The system in question is configured to setup a bridge called storage0 to
> bridge DomUs with the tagged vlan with the ID 60.
> 
> The network configuration looks as follows:
> 
> [root@king ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0.60 
> DEVICE=eth0.60
> PHYSDEV=eth0
> BOOTPROTO=static
> ONBOOT=yes
> VLAN=yes
> BRIDGE=storage0

I used almost the same configuration (the same except I am having it connected to eth1 port instead of eth0).

> [root@king ~]# cat /etc/sysconfig/network-scripts/ifcfg-storage0 
> DEVICE=storage0
> BOOTPROTO=static
> IPADDR=172.16.4.100
> NETMASK=255.255.254.0
> ONBOOT=yes
> TYPE=Bridge

For that I did use DHCP:
DEVICE=br0
BOOTPROTO=dhcp
ONBOOT=yes
TYPE=Bridge 

> [root@king ~]# 
> 
> After configuring the changes at runtime and calling service network restart,
> the network configuration looks as expected and works.

Well, I don't really know what setup are you having. According to presence of ifcfg-storage0 file in network-scripts you are having the bridge set up manually, right ? However, since you are writing about change of eth0 name to peth0 in /proc/net/vlan/config it seems you are using automatic network bridge creation in xend-config.sxp as well, could you please look for the '(network-script' entry in the /etc/xen/xend-config.sxp file?

If you want to use manual bridge setup (like you want to here according to presence of ifcfg-storage0 file) you have to disable automatic network bridge creation in xend-config file by setting "(network-script '/bin/true')" in the /etc/xen/xend-config.sxp configuration file instead of "(network-script 'network-bridge')" which is set by default.

> After bootup however the hosts on the network 172.16.4.0/23 are unreachable.
> 
> Analysis shows the following difference:
> 
> 
> [root@king ~]# cat /proc/net/vlan/config 
> VLAN Dev name    | VLAN ID
> Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
> eth0.60        | 60  | eth0
> [root@king ~]# 
> 
> vs.
> 
> [root@king ~]# cat /proc/net/vlan/config
> VLAN Dev name | VLAN ID
> Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
> eth0.60 | 60 | peth0
> [root@king ~]# 
> 

Like I wrote above this looks like you are having both xen automatic network bridge enabled and using the manual bridge setup. When I disabled the automatic network bridge creation as described above and used the configuration files for manual bridge and VLAN configuration it was working fine for me even to access the same subnet.

Since it looks like you are having the manual bridge setup done but the automatic network bridge creation for xen is enabled too (as it should not). Could you please try to change the "(network-script 'network-bridge')" line to "(network-script '/bin/true')" to disable the network bridge creation, reboot and try again?

Thanks a lot,
Michal

Hmm. I checked. The system in question is indeed using the automatic bridging in addition to one manual bridge.

Let's try the fully manual step.

(In reply to comment #6)
> Hmm. I checked. The system in question is indeed using the automatic bridging
> in addition to one manual bridge.
> 
> Let's try the fully manual step.    

Yeah, according to the scripts you've shared with us (ifcfg-storage0) you're using the manual bridge configuration. You can't be using both manual and automatic bridge configuration at the same time so please disable it and try rebooting your dom0.

Let me know the test results,
Michal

Andreas, anything new with this one? Did you try the fully manual settings with no automatic bridge creation enabled?

Thanks,
Michal

This is duplicate of bz 514492. network-bridge script does not change vlan based on bridged interface. You can try fixed script attached to that bz, it should fix your problem.

*** This bug has been marked as a duplicate of bug 514492 ***