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-users

Re: [Xen-users] Yet another question about multiple NICs

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Yet another question about multiple NICs
From: Simon Hobson <linux@xxxxxxxxxxxxxxxx>
Date: Fri, 17 Dec 2010 12:03:47 +0000
Delivery-date: Fri, 17 Dec 2010 04:05:39 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D0B4544.4050202@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <4D0B4213.50303@xxxxxxxxxxx> <4D0B4544.4050202@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Felix Kuperjans wrote:

- Is your bridge really named equally to your network interface (i.e.
both eth0) or is the network interface renamed? Probably something got
confused there (ip addr will show it anyway).

Don't know if it's a "Debian thing" or not, but my setup is the same - eth0 will get renamed to peth0, and a bridge created called eth0.


Philippe Combes:

 In /etc/xen/xend-config.sxp:
  (network-script network-bridge-wrapper)
 /etc/xen/scripts/network-bridge-wrapper:
  #!/bin/bash
  dir=$(dirname "$0")
  "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=eth0
  "$dir/network-bridge" "$@" vifnum=1 netdev=eth1 bridge=eth1
 In domU configuration file:
  vif = [ 'mac=00:16:3E:55:AF:C2,bridge=eth0',
 'mac=00:16:3E:55:AF:C3,bridge=eth1' ]

That looks just like mine.

This is just a bit of a hunch, but if you are still having the problem, can you do this :

At the other network device, run "arp -an" and see what MAC address is reported for the device (Dom0 or DomU) that's pinging it. Do this twice, when one is working, and when the other is working - the entries you are interested in are the ones for the IPs of your Dom0 and DomU

Also, I assume you have checked that the Dom0 and DomU are getting different IPs haven't you ?

--
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.

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