WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Fwd: Re: [Xen-users] Random swap of interfaces at domU start

To: "Xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Fwd: Re: [Xen-users] Random swap of interfaces at domU startup
From: Daniele Palumbo <daniele@xxxxxxxxxxxx>
Date: Wed, 24 Jan 2007 13:13:06 +0100
Delivery-date: Wed, 24 Jan 2007 04:11:53 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.4
maybe a developer can explain that...

----------  Forwarded Message  ----------

Subject: Re: [Xen-users] Random swap of interfaces at domU startup
Date: Tuesday 23 January 2007 13:24
From: Daniele Palumbo <daniele@xxxxxxxxxxxx>
To: xen-users@xxxxxxxxxxxxxxxxxxx

On Thursday 18 January 2007 22:24, Frédéric VANNIÈRE wrote:
> I don't think so. The problem comes from xend, it doesn't plug the
> vif interface on the right bridge.
>
> I guess the problem comes from dict handling in Python, default dicts
> are not ordered

i have same problem too, and 3.0.4 too (but seems, at first look, that also
3.0.3 got it)
and i agree (almost) with you, but i think that is not something
like "unordered" (you can see correct order in vif0.0, vif0.1).
my opinion (without looking at code) is that there is concurrent thread that
setup bridge, and so who is running faster will be setup as eth0.

> This is OK :
>    (XendDomainInfo:1195) {'bridge': 'xenbr0', 'mac': '00:26:3E:7B:0B:
> 24', 'uuid': '17ccddf1-17ee-87a6-9534-a8439402f38a', 'ip':
> '192.168.2.145'}
>   (XendDomainInfo:1195) {'bridge': 'xenbr1', 'mac': '00:26:3E:7B:0B:
> 25', 'uuid': 'b96f77b6-b310-7f21-cdfc-a9a598c85790', 'ip': '10.1.0.21'}
>
> This is NOT OK :
>   (XendDomainInfo:1195)  {'bridge': 'xenbr1', 'mac': '00:26:3E:7B:0B:
> 25', 'uuid': '661e6a7e-be77-28ce-180d-fca88aa826ab', 'ip': '10.1.0.21'}
>   (XendDomainInfo:1195)  {'bridge': 'xenbr0', 'mac': '00:26:3E:7B:0B:
> 24', 'uuid': '87f327a3-0544-f76a-81f8-6edd5ac7b6f5', 'ip':
> '192.168.2.145'}

just other logs:

config file:
vif = [ 'bridge=xenbr1', 'bridge=xenbr1.600', 'bridge=xenbr1.14' ]

in attachment: xend.log, notable lines:
--
['device', ['vif', ['bridge', 'xenbr1']]], ['
device', ['vif', ['bridge', 'xenbr1.600']]], ['device', ['vif',
['bridge', 'xenbr1.14']]]
[...]
createDevice: vif : {'bridge': 'xenbr1'
[...]
createDevice: vif : {'bridge': 'xenbr1.14',
[...]
createDevice: vif : {'bridge': 'xenbr1.600',
[...]
--
as you can see, eth1 and eth2 are swapped.
but in a precedent boot, eth0 and eth1 were swapped.

- messages -
Jan 23 12:19:13 xen2 logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/2/2049
Jan 23 12:19:13 xen2 logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/2/2065
Jan 23 12:19:13 xen2 logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/2/0
Jan 23 12:19:13 xen2 logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/2/1
Jan 23 12:19:13 xen2 logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/2/2050
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/2/2
Jan 23 12:19:14 xen2 [ 2832.403309] device vif2.1 entered promiscuous mode
Jan 23 12:19:14 xen2 [ 2832.407399] device vif2.0 entered promiscuous mode
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif2.1, bridge xenbr1.14.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/2/1/hotplug-status connected to xenstore.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif2.0, bridge xenbr1.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/2/0/hotplug-status connected to xenstore.
Jan 23 12:19:14 xen2 [ 2832.428236] device vif2.2 entered promiscuous mode
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/block: Writing
backend/vbd/2/2065/physical-device fd:5 to xenstore.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif2.2, bridge xenbr1.600.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/block: Writing
backend/vbd/2/2065/hotplug-status connected to xenstore.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/2/2/hotplug-status connected to xenstore.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/block: Writing
backend/vbd/2/2050/physical-device fd:9 to xenstore.
Jan 23 12:19:14 xen2 logger: /etc/xen/scripts/block: Writing
backend/vbd/2/2050/hotplug-status connected to xenstore.
Jan 23 12:19:15 xen2 logger: /etc/xen/scripts/block: Writing
backend/vbd/2/2049/physical-device fd:8 to xenstore.
Jan 23 12:19:15 xen2 logger: /etc/xen/scripts/block: Writing
backend/vbd/2/2049/hotplug-status connected to xenstore.

bye
d.

-------------------------------------------------------

Attachment: swapping_interface.xend.log
Description: Text Data

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