[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] XEN - Broadcom issue: survey

> this driver is the one relased by DELL on Nov. 11, and I have packet drop. 
> The same with driver 1.5.1c from broadcom
> The strange thing is that TX-DRP is 0 until I start a domain. Since I start 
> an HVM, TX-DRP for its vif start incresing.
> If I start an PV machine, it drop only 20 packets and then stop. No more 
> TX-DRP at all...
Yes, that's normal and expected behaviour.  If you try and send a
packet over a PV network interface to a domain which hasn't loaded the
PV network driver, the packet will be dropped and the TX-DRP statistic
will be incremented.  PV domains will therefore see a small number of
packets dropped at boot time, while HVM domains will see ongoing
packet drop for as long as the domain remains alive.  For an HVM
domain, you probably want to look at the tap device rather than the


> So, to isolate the problem, it is related to HVM machine only. At least in 
> my case.
> Ivan
> Pezza wrote:
>> Hey,
>> please note that if you're using the tg3 driver, it means you're using
>> NetXTreme *not* NetXTreme II (the latter is using the 5708/5706 chipsets,
>> the former some previous releases). The problem has been observed (but I'd 
>> like some confirmations here ;-))
>> using the bnx2 driver, which is specific to NetEXtreme II.
>> To make sure what driver/version/firmware you're using you can run 
>> 'ethtool
>> -i eth0' (replace eth0 with the ethernet device you want to show).
>> In my case, the "bad" machine shows:
>> [root@sofia ~]# ethtool -i peth0
>> driver: bnx2
>> version: 1.5.10c
>> firmware-version: 1.9.3
>> bus-info: 0000:03:00.0
>> while the "good" machine shows:
>> [root@camogli scripts]# ethtool -i eth0
>> driver: bnx2
>> version: 1.5.1c
>> firmware-version: 2.9.1
>> bus-info: 0000:08:00.0
>> As I said before, the only relevant difference I can find between the 2
>> machines is the eth0 firmware version, but I don't now if and how I can
>> update it on the other one (ref to my previous message for the complete
>> details on the good and bad machine configuration).
>>                              M.
>> mangoo wrote:
>>> Ivan Porro schrieb:
>>>> I totally agree with Luc Boudreau about this problem.
>>>> On modern branded server they ALL use Broadcom chipset... I must admit 
>>>> that:
>>>> a) lot of people are experiencing the problem but can tolerate it
>>>> or
>>>> b) someone already experienced this problem and solved it
>>> Too bad you started a new topic without even trying to describe what your 
>>> problem with broadcom chipsets is?
>>> I'm running Xen 3.1 (2.6.18 kernel), compiled from sources, on HP 
>>> ProLiant DL320 G3. It uses tg3 for its network cards.
>>> Works fine.
>>> 06:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
>>> Gigabit Ethernet (rev 10)
>>> 06:01.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704 
>>> Gigabit Ethernet (rev 10)
>>> -- 
>>> Tomasz Chmielewski
>>> http://lists.wpkg.org
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users
> -- 
> http://www.bio.dist.unige.it
> voice: +39 010 353 2789
> fax:   +39 010 353 2948
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

Attachment: signature.asc
Description: Digital signature

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.