Xen users - May 2007 - order of network interfaces in domU messed up?

Hi,

until now, i have been using Xen 3.0.2. Now i upgraded to Xen 3.0.4.

Can anybody confirm, that the ordner in the config files for the network
interfaces has not changed?

My config file used to read:
vif = [ ''bridge=xenbr0'', ''bridge=xenbr1'' ]

So inside the DomU, eth0 was attached to xenbr0 on the host and eth1 was
attached to xenbr1.

Now i upgraded to Xen 3.0.4.
Not it must read:
vif = [ ''bridge=xenbr1'', ''bridge=xenbr0'' ]


And i''m not even quite sure, that the order of the network-interfaces
is
really deterministic. Actually, the old config worked on first try. And
suddently didn''t. Then i debugged and now it only works with inverted
order.


Any idea, what''s going on?


Thanks,
  Sven Köhler



_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hi Sven,

I can confirm the re-ordering after upgrade to Xen 3.0.4!
Unfortunately it is not really this easy and I agree, that it looks very
random...

I have 3 interfaces in my Xen-Config:

vif = [ ''mac=00:16:3e:01:00:12, bridge=xenbr0'',
        ''mac=00:17:3e:01:00:12, bridge=xenbr1'',
        ''mac=00:18:3e:01:00:12, bridge=xenbr1'' ]

And since Xen 3.0.4 I get the following order in DomU:

# ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:16:3e:01:00:12 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:18:3e:01:00:12 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:17:3e:01:00:12 brd ff:ff:ff:ff:ff:ff


Anyone with better experience in vif ordering to help us?

Sven.


Sven Köhler wrote:
> 
> Hi,
> 
> until now, i have been using Xen 3.0.2. Now i upgraded to Xen 3.0.4.
> 
> Can anybody confirm, that the ordner in the config files for the network
> interfaces has not changed?
> 
> My config file used to read:
> vif = [ ''bridge=xenbr0'',
''bridge=xenbr1'' ]
> 
> So inside the DomU, eth0 was attached to xenbr0 on the host and eth1 was
> attached to xenbr1.
> 
> Now i upgraded to Xen 3.0.4.
> Not it must read:
> vif = [ ''bridge=xenbr1'',
''bridge=xenbr0'' ]
> 
> 
> And i''m not even quite sure, that the order of the
network-interfaces is
> really deterministic. Actually, the old config worked on first try. And
> suddently didn''t. Then i debugged and now it only works with
inverted
> order.
> 
> 
> Any idea, what''s going on?
> 
> 
> Thanks,
>   Sven Köhler
> 
> 
>  
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
> 

-- 
View this message in context:
http://www.nabble.com/order-of-network-interfaces-in-domU-messed-up--tf3682871.html#a10407804
Sent from the Xen - User mailing list archive at Nabble.com.


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

With a NetBSD DomU and Xen 3.0.4-1, the assignment is comparable to a
slot machine. The oddest part is that this DomU is meant to be my
gateway, if I ever figure this out.

François

vif = [ ''vifname=peru1, mac=00:16:3e:c3:c3:c1, bridge=xenbr1'',
\
                ''vifname=peru2, mac=00:16:3e:c3:c3:c2,
bridge=xenbr2'' ]


2007/5/10, Sven Giermann <giermann@funke.de>:
>
> Hi Sven,
>
> I can confirm the re-ordering after upgrade to Xen 3.0.4!
> Unfortunately it is not really this easy and I agree, that it looks very
> random...
>
> I have 3 interfaces in my Xen-Config:
>
> vif = [ ''mac=00:16:3e:01:00:12, bridge=xenbr0'',
>         ''mac=00:17:3e:01:00:12, bridge=xenbr1'',
>         ''mac=00:18:3e:01:00:12, bridge=xenbr1'' ]
>
> And since Xen 3.0.4 I get the following order in DomU:
>
> # ip addr
> 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>     inet 127.0.0.1/8 scope host lo
> 2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>     link/ether 00:16:3e:01:00:12 brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>     link/ether 00:18:3e:01:00:12 brd ff:ff:ff:ff:ff:ff
> 4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>     link/ether 00:17:3e:01:00:12 brd ff:ff:ff:ff:ff:ff
>
>
> Anyone with better experience in vif ordering to help us?
>
> Sven.
>
>
> Sven Köhler wrote:
> >
> > Hi,
> >
> > until now, i have been using Xen 3.0.2. Now i upgraded to Xen 3.0.4.
> >
> > Can anybody confirm, that the ordner in the config files for the
network
> > interfaces has not changed?
> >
> > My config file used to read:
> > vif = [ ''bridge=xenbr0'',
''bridge=xenbr1'' ]
> >
> > So inside the DomU, eth0 was attached to xenbr0 on the host and eth1
was
> > attached to xenbr1.
> >
> > Now i upgraded to Xen 3.0.4.
> > Not it must read:
> > vif = [ ''bridge=xenbr1'',
''bridge=xenbr0'' ]
> >
> >
> > And i''m not even quite sure, that the order of the
network-interfaces is
> > really deterministic. Actually, the old config worked on first try.
And
> > suddently didn''t. Then i debugged and now it only works with
inverted
> > order.
> >
> >
> > Any idea, what''s going on?
> >
> >
> > Thanks,
> >   Sven Köhler
> >
> >
> >
> > _______________________________________________
> > Xen-users mailing list
> > Xen-users@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>
> --
> View this message in context:
http://www.nabble.com/order-of-network-interfaces-in-domU-messed-up--tf3682871.html#a10407804
> Sent from the Xen - User mailing list archive at Nabble.com.
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users