Re: [Xen-API] bnx2 driver failed in linux-2.6.18.8-xen-3.4.2, Dell R610

[Luwei Cheng <chengluwei@xxxxxxxxx>]

Hello Pasi,

I have upgraded to Linux 2.6.32.13, with patch 

http://gentoo-xen-kernel.googlecode.com/files/xen-patches-2.6.32-2.tar

the udev I am using is:

[root@ ~]# udevinfo -V

udevinfo, version 095

Here is the output of xm log:

DEBUG (DevController:629) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status.

INFO (XendDomain:1182) Domain centos.5-4.x86 (2) unpaused.

DEBUG (XendDomainInfo:2732) XendDomainInfo.destroy: domid=2

DEBUG (XendDomainInfo:2207) Destroying device model

DEBUG (XendDomainInfo:2214) Releasing devices

DEBUG (XendDomainInfo:2227) Removing vif/0

DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0

DEBUG (XendDomainInfo:2227) Removing vbd/2049

DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = tap, device = vbd/2049

DEBUG (XendDomainInfo:2227) Removing console/0

DEBUG (XendDomainInfo:1134) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0

DEBUG (XendDomainInfo:2212) No device model

DEBUG (XendDomainInfo:2214) Releasing devices

Any idea?

Thanks,

Luwei

On Mon, Nov 15, 2010 at 2:57 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:

On Mon, Nov 15, 2010 at 06:46:18AM +0800, Luwei Cheng wrote:
>    Hello Pasi,
>    Thanks for the reply. I have updated XEN to version 4.0 with LInux kernel
>    2.6.31.8. (I also tried xen-3.4.2)

You shouldn't use 2.6.31.*, it's deprecated and unsupported.
xen/stable-2.6.32.x branch is the new supported dom0 capable kernel.
(2.6.32.25 is the newest version).

>    Luckily it can boot and bnx2 NIC works.
>    But another problem happens: guest domain can not boot correctly, shows
>    "Device 0 (vif) could not be connected."
>    I have almost searched the whole internet to find the solution but none
>    worked.
>    Some people suggest "/sbin/start_udev", but it does not work for my
>    machine.
>    Any idea ??

Try reading "xm log" to see more info about the problem.

-- Pasi

>    Thanks in advance.
>    Best,
>    Luwei

>    On Sun, Nov 14, 2010 at 3:57 AM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote:
>
>      On Sat, Nov 13, 2010 at 04:43:25AM +0800, Luwei Cheng wrote:
>      >    Hello Bruce,
>      >    Thanks for your reply. In my kernel, I did not
>      >    find CONFIG_FIRMWARE_IN_KERNEL.
>      >    There are only 4 options related to firmware in my kernel:
>      >    CONFIG_PREVENT_FIRMWARE_BUILD=y
>      >    CONFIG_HOSTAP_FIRMWARE=y
>      >    CONFIG_HOSTAP_FIRMWARE_NVRAM=y
>      >    CONFIG_FIRMWARE_EDID=y
>      >    Any idea?
>

>      [2]http://wiki.xen.org/xenwiki/XenParavirtOps

>
>      especially read the troubleshooting section.
>      It has instructions how to build the kernel,
>      and also it has reference .config files with working kernel
>      configuration.
>
>      -- Pasi
>
>      >    Best,
>      >    -Luwei
>      >    On Sat, Nov 13, 2010 at 4:26 AM, Bruce Edge

>      <[1][3]bruce.edge@xxxxxxxxx>

>      >    wrote:
>      >
>      >      On Fri, Nov 12, 2010 at 12:10 PM, Luwei Cheng

>      <[2][4]chengluwei@xxxxxxxxx>

>      >      wrote:
>      >      > So many issues I did not expect to have... I think I need a
>      2.6.18
>      >      stable
>      >      > kernel to run.
>      >      > Actually I have only ONE step to succeed in 2.6.18.8. Any one
>      who
>      >      knows how
>      >      > to patch bnx2 dirver?
>      >      > Deep thanks!
>      >      > --Luwei
>      >      >
>      >      > On Sat, Nov 13, 2010 at 2:05 AM, Luwei Cheng

>      <[3][5]chengluwei@xxxxxxxxx>

>      >      wrote:
>      >      >>
>      >      >> Yes, I am already in progress to install 2.6.32 with long time
>      to git
>      >      >> clone... hope not too much trouble shooting:-)
>      >      >> Anyway, if there's any patch to 2.6.18.8-bnx2 driver, I'd like
>      it
>      >      more.
>      >      >> Regards,
>      >      >> Luwei
>      >
>      >      Not sure if this is related to your specific problem, but to use
>      a
>      >      BNX2 NIC I need to enable
>      >         CONFIG_FIRMWARE_IN_KERNEL=y
>      >      in order to pull the BNX2 firmware into the kernel, otherwise it
>      >      complains that it can't find the firmware at boot time.
>      >
>      >      -Bruce
>      >      >>
>      >      >> On Sat, Nov 13, 2010 at 1:56 AM, Konrad Rzeszutek Wilk

>      >      >> <[4][6]konrad.wilk@xxxxxxxxxx> wrote:
>      >      >>>
>      >      >>> On Sat, Nov 13, 2010 at 01:19:03AM +0800, Luwei Cheng wrote:
>      >      >>> > Hello Konrad,
>      >      >>> >
>      >      >>> > Thanks for your reply to enlighten me.
>      >      >>> >
>      >      >>> > This is almost the first time that I compile XenLinux from
>      source.
>      >      To
>      >      >>> > play
>      >      >>> > safe, I just downloaded the source code from

>      [5][7]www.xen.org.

>      >      >>> > Is 2.6.32-PVOPS already stable kernel? Is there any
>      document to
>      >      follow
>      >      >>> > so
>      >      >>> > that I won't miss some steps? Thanks!
>      >      >>>
>      >      >>> Look on Google for "Wiki PVOPS" and it will direct you the
>      Wiki on
>      >      how to
>      >      >>> do it.
>      >      >>
>      >      >
>      >      >
>      >      > _______________________________________________
>      >      > xen-api mailing list

>      >      > [6][8]xen-api@xxxxxxxxxxxxxxxxxxx
>      >      > [7][9]http://lists.xensource.com/mailman/listinfo/xen-api
>      >      >
>      >      >
>      >
>      > References
>      >
>      >    Visible links
>      >    1. mailto:[10]bruce.edge@xxxxxxxxx
>      >    2. mailto:[11]chengluwei@xxxxxxxxx
>      >    3. mailto:[12]chengluwei@xxxxxxxxx
>      >    4. mailto:[13]konrad.wilk@xxxxxxxxxx
>      >    5. [14]http://www.xen.org/
>      >    6. mailto:[15]xen-api@xxxxxxxxxxxxxxxxxxx
>      >    7. [16]http://lists.xensource.com/mailman/listinfo/xen-api
>      > _______________________________________________
>      > xen-api mailing list
>      > [17]xen-api@xxxxxxxxxxxxxxxxxxx
>      > [18]http://lists.xensource.com/mailman/listinfo/xen-api
>
> References
>
>    Visible links
>    1. mailto:pasik@xxxxxx
>    2. http://wiki.xen.org/xenwiki/XenParavirtOps

>    3. mailto:bruce.edge@xxxxxxxxx
>    4. mailto:chengluwei@xxxxxxxxx
>    5. mailto:chengluwei@xxxxxxxxx
>    6. mailto:konrad.wilk@xxxxxxxxxx
>    7. http://www.xen.org/
>    8. mailto:xen-api@xxxxxxxxxxxxxxxxxxx

>    9. http://lists.xensource.com/mailman/listinfo/xen-api
>   10. mailto:bruce.edge@xxxxxxxxx
>   11. mailto:chengluwei@xxxxxxxxx
>   12. mailto:chengluwei@xxxxxxxxx
>   13. mailto:konrad.wilk@xxxxxxxxxx
>   14. http://www.xen.org/
>   15. mailto:xen-api@xxxxxxxxxxxxxxxxxxx
>   16. http://lists.xensource.com/mailman/listinfo/xen-api
>   17. mailto:xen-api@xxxxxxxxxxxxxxxxxxx
>   18. http://lists.xensource.com/mailman/listinfo/xen-api

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api