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] NOT RESOLVED: Broadcom NetXtreme II (DELL 1950)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] NOT RESOLVED: Broadcom NetXtreme II (DELL 1950)
From: "Fajar A. Nugraha" <fajar@xxxxxxxxxxxxx>
Date: Mon, 08 Oct 2007 09:12:14 +0700
Delivery-date: Sun, 07 Oct 2007 19:13:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47084844.8030702@xxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <47082F9B.3000300@xxxxxxxxxxxxxxxx> <47084844.8030702@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.6 (X11/20070728)
Stefan de Konink wrote:
> Hi,
>
> Kris S. Amundson schreef:
> > Upgrading the bnx2 driver is the key.  I came to find bnx2 is included
> > in the initrd.  Debian comes with 1.4.44 and Ubuntu 1.4.45 of the
> > driver.  As of this writing 1.5.10c is the latest from Broadcom and is
> > what I ended up using.
>

Strange. I thought network drivers were not supposed to be included in
the initrd.

>
> Just updated the driver, verified it was loaded (by version), changed
> the config of xend back to bridged. Restarted Xend, bang, bridge kills
> the interface.
>

One question. On your configuration, does bridge works on native Linux?

>
> So my basic assumption:
> - A bridge should be placed automatically by the default scripts over
> something like peth0/eth0 and the vif interface between the virtual
> hosts. The peth0/eth0 is the interface you receive your netwerk
> connections on.
>
>

I had problems with some models of Broadcom NICs (both tg3 and bnx2
drivers). Other than that, I didn't like the way xend start script was
changing network device names, so what I did was :
- upgrade the drivers
- changed network-script to /bin/true on xend-config.sxp
- setup bridge using standard RHEL config files
(/etc/sysconfig/network-scripts/ifcfg-br0)

I find this approach works best on my setup. Using RHEL5, which includes
Xen-3.0.3.

Regards,

Fajar

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