Jignesh Patel
2010-Sep-22 22:21 UTC
[Xen-users] Xen-4.0.1 PCI cannot get nework card to work
Hello,
I need help get working my NIC with Xen domU.
I can see the NIC card from domU but cannot get it to work. The same network
card will work fine on the dom0.
When I unplug and plug the network cable from the NIC, I can see in the
system log:
[ 151.770678] eth0: link down
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
But when I do "/etc/init.d/networking restart", I cannot see DHCP
request
coming to my router.
The same NIC will work fine on dom0.
Can some one check my configuration ?
I know that PCI hide works as I can see
# xm pci-list-assignable-devices
0000:08:01.0
-----------dom0------------------------
o# cat menu.lst | grep -v \#
default 0
timeout 5
color cyan/blue white/blue
title Xen 4.0-amd64 / Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
root (hd0,0)
kernel /boot/xen-4.0-amd64.gz loglvl=all guest_loglvl=all
module /boot/vmlinuz-2.6.32-5-xen-amd64
root=UUID=41b96025-ba58-4938-b118-a492542ac786 ro console=tty0
xen-pciback.permissive xen-pciback.hide=(08:01.0)
module /boot/initrd.img-2.6.32-5-xen-amd64
title Debian GNU/Linux, kernel 2.6.32-5-xen-amd64
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-5-xen-amd64
root=UUID=41b96025-ba58-4938-b118-a492542ac786 ro quiet
initrd /boot/initrd.img-2.6.32-5-xen-amd64
title Debian GNU/Linux, kernel 2.6.32-5-xen-amd64 (single-user
mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-5-xen-amd64
root=UUID=41b96025-ba58-4938-b118-a492542ac786 ro single
initrd /boot/initrd.img-2.6.32-5-xen-amd64
title Debian GNU/Linux, kernel 2.6.26-2-amd64
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-amd64
root=UUID=41b96025-ba58-4938-b118-a492542ac786 ro quiet
initrd /boot/initrd.img-2.6.26-2-amd64
title Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode)
root (hd0,0)
kernel /boot/vmlinuz-2.6.26-2-amd64
root=UUID=41b96025-ba58-4938-b118-a492542ac786 ro single
initrd /boot/initrd.img-2.6.26-2-amd64
----------------------------------------------------------------------------------
--------------------------domU
config----------------------------------------------
#
# Configuration file for the Xen instance sangomatest, created
# by xen-tools 4.2rc1 on Mon Sep 13 13:13:06 2010.
#
#
# Kernel + memory size
#
kernel = ''/boot/vmlinuz-2.6.32-5-xen-amd64''
ramdisk = ''/boot/initrd.img-2.6.32-5-xen-amd64''
vcpus = ''1''
memory = ''1024''
#
# Disk device(s).
#
root = ''/dev/xvda2 ro''
disk = [
''file:/home/xen//domains/sangomatest/disk.img,xvda2,w'',
''file:/home/xen//domains/sangomatest/swap.img,xvda1,w'',
]
#
# Physical volumes
#
#
# Hostname
#
name = ''sangomatest''
#
# Networking
#
dhcp = ''dhcp''
#vif = [ ''mac=00:16:3E:C3:C3:95'' ]
#
# Behaviour
#
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
iommu=''soft''
pci=[''08:01.0'']
swiotlb=''force''
-----------------------------------------------------------------------------------------------------------------------------------------------------
---additional info---
dpkg -l | grep xen
ii libxenstore3.0 4.0.1-1 Xenstore
communications library for Xen
ii linux-headers-2.6.32-5-common-xen 2.6.32-22 Common
header files for Linux 2.6.32-5-xen
ii linux-headers-2.6.32-5-xen-amd64 2.6.32-22 Header
files for Linux 2.6.32-5-xen-amd64
ii linux-image-2.6.32-5-xen-amd64 2.6.32-21 Linux
2.6.32 for 64-bit PCs, Xen dom0 support
ii xen-hypervisor-4.0-amd64 4.0.1-1 The Xen
Hypervisor on AMD64
ii xen-linux-system-2.6.32-5-xen-amd64 2.6.32-21 Xen
system with Linux 2.6.32 on 64-bit PCs
ii xen-shell 1.8-3 Console
based Xen administration utility
ii xen-tools 4.2~rc1-1 Tools to
manage Xen virtual servers
ii xen-utils-4.0 4.0.1-1 XEN
administrative tools
ii xen-utils-common 4.0.0-1 XEN
administrative tools - common files
ii xenstore-utils 4.0.1-1 Xenstore
utilities for Xen
log files
------------------------------------------------------------------
dom0 system log : http://pastebin.com/dm8zah43
<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.
Thank you,
Jignesh
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Todd Deshane
2010-Sep-23 01:49 UTC
Re: [Xen-users] Xen-4.0.1 PCI cannot get nework card to work
Hi Jignesh, Some requests for more info within. On Wed, Sep 22, 2010 at 6:21 PM, Jignesh Patel <j4sangoma@gmail.com> 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. Thanks, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Todd Deshane
2010-Sep-23 02:17 UTC
Re: [Xen-users] Xen-4.0.1 PCI cannot get nework card to work
On Wed, Sep 22, 2010 at 9:49 PM, Todd Deshane <deshantm@gmail.com> wrote:> those threads might help or give debugging tips.Also, just in case you missed it: http://wiki.xensource.com/xenwiki/XenPCIpassthrough There are a few special cases where things might not work. Thanks, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jignesh Patel
2010-Sep-27 16:33 UTC
Re: [Xen-users] Xen-4.0.1 PCI cannot get nework card to work
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"
online = "1"
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,
Jignesh
On Wed, Sep 22, 2010 at 9:49 PM, Todd Deshane <deshantm@gmail.com> wrote:
> Hi Jignesh,
>
> Some requests for more info within.
>
> On Wed, Sep 22, 2010 at 6:21 PM, Jignesh Patel <j4sangoma@gmail.com>
> 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.
>
> Thanks,
> Todd
>
> --
> Todd Deshane
> http://todddeshane.net
> http://runningxen.com
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Jignesh Patel
2010-Sep-30 15:37 UTC
Re: [Xen-users] Xen-4.0.1 PCI cannot get nework card to work
Hi Todd, I have my NIC working with Xen 4.0 now. I have following config that works: for dom0 , menu.lst root (hd0,0) kernel /boot/xen-4.0-amd64.gz loglvl=all guest_loglvl=all module /boot/vmlinuz-2.6.32-5-xen-amd64 root=UUID=41b96025-ba58-4938-b118-a492542ac786 ro console=tty0 irqpoll xen-pciback.permissive xen-pciback.hide=(0000:06:04.0)(0000:08:01.0) pci=resource_alignment=0000:06:04.0;0000:08:01.0 and following additional configuration in domU config file. ---------------------------- pci=[''06,04,0'',''08,01,0''] extra = ''swiotlb=force iommu=soft'' -------------------------- It was the syntax that was not right. Thank you for your suggestion. Cheers, Jignesh On Mon, Sep 27, 2010 at 12:33 PM, Jignesh Patel <j4sangoma@gmail.com> wrote:> 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" > online = "1" > 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, > > Jignesh > > > > On Wed, Sep 22, 2010 at 9:49 PM, Todd Deshane <deshantm@gmail.com> wrote: > >> Hi Jignesh, >> >> Some requests for more info within. >> >> On Wed, Sep 22, 2010 at 6:21 PM, Jignesh Patel <j4sangoma@gmail.com> >> 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. >> >> Thanks, >> Todd >> >> -- >> Todd Deshane >> http://todddeshane.net >> http://runningxen.com >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users