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

Re: [Xen-users] Xen-4.0.1 PCI cannot get nework card to work

  • To: deshantm@xxxxxxxxx
  • From: Jignesh Patel <j4sangoma@xxxxxxxxx>
  • Date: Mon, 27 Sep 2010 12:33:16 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 27 Sep 2010 09:34:45 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NXZx2RV3PIqa9qrpuL8TNiTSpTqF0h8E3HLGx3T1WyELJxWCnOSPqFYZOPFPg9F/ia PgDyH3auFos49oZ0Wr59xJz9caOK/ENKBU9HA5ds51dG4A37wGbjgynl6kSC6NBHpJXy UCNw0eBffNre7NvHX9/z8q6jWebZVTeuqL4aM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi Todd,
1) lspci -vvv on the domU guest
# lspci -vvv
00:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    Subsystem: Realtek Semiconductor Co., Ltd. RT8139
    Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Latency: 32 (8000ns min, 16000ns max)
    Interrupt: pin A routed to IRQ 22
    Region 0: I/O ports at 1000 [size=256]
    Region 1: Memory at e2000000 (32-bit, non-prefetchable) [size=256]
    Expansion ROM at e3400000 [disabled] [size=64K]
    Capabilities: [50] Power Management version 2
        Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
        Status: D0 PME-Enable- DSel=0 DScale=0 PME-
    Kernel driver in use: 8139too
    Kernel modules: 8139too, 8139cp

2) the tail of the dmesg just after running the dhcp client (dhclient on debian)

 I don't have dhcp client running on debian (dom0). The IP is provided by the gateway router.
 On Gateway Router log I don't see DHCP request from domU when I use the Realtek card with pci passthrough.

From xenstore-ls :

 pci = ""
     2 = ""
      0 = ""
       domain = "sangomatest"
       key-0 = "08:01.0"
       vdevfn-0 = "100"
       uuid = "00ca7504-f956-8a08-4e0d-b67a526a16f3"
       dev-0 = "0000:08:01.0"
       frontend = "/local/domain/2/device/pci/0"
       state = "4"
       >        frontend-id = "2"
       uuid-0 = "089bc4f9-9e74-f7d7-32a4-54d164c1d9af"
       num_devs = "1"
       vdev-0 = "0000:00:00.00"
       state-0 = "3"
       root-0 = "0000:00"
       root_num = "1"

Could this be configuration issue ?

Thank you,


On Wed, Sep 22, 2010 at 9:49 PM, Todd Deshane <deshantm@xxxxxxxxx> wrote:
Hi Jignesh,

Some requests for more info within.

On Wed, Sep 22, 2010 at 6:21 PM, Jignesh Patel <j4sangoma@xxxxxxxxx> wrote:
> log files
> ------------------------------------------------------------------
> dom0 system log : http://pastebin.com/dm8zah43
> dom0 system info + lscpi -v : http://pastebin.com/24DjJczv
> Xen  dmesg : http://pastebin.com/bkZSGsv7
> domU system log: http://pastebin.com/aHHur2m1
> --------------------------------------------------------------------------------
> Let me know if additional information is needed.

Could you also provide the following?

1) lspci -vvv on the domU guest

2) the tail of the dmesg just after running the dhcp client (dhclient on debian)

You may also want to do some reading on threads related to xenstore-ls and pci

See for example: http://xen.markmail.org/search/?q=xenstore-ls+pci

You may be able to provide more information on specifically what is
being created for the device in xenstore. I don't know the specifics,
but those threads might help or give debugging tips.

Hope that helps.


Todd Deshane

Xen-users mailing list



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