[prev in list] [next in list] [prev in thread] [next in thread]
List: xen-users
Subject: Re: [Xen-users] Xen-4.0.1 PCI cannot get nework card to work
From: Jignesh Patel <j4sangoma () gmail ! com>
Date: 2010-09-30 15:37:22
Message-ID: AANLkTimXYPsBL83ZYsuBGth-HhCorjBJ_cAgXnjKeEeD () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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
>>
>
>
[Attachment #5 (text/html)]
Hi Todd,<div><br></div><div>I have my NIC working with Xen 4.0 \
now.</div><div><br></div><div>I have following config that \
works:</div><div><br></div><div>for dom0 , \
menu.lst</div><div><br></div><div><div>root (hd0,0)</div> <div>kernel \
/boot/xen-4.0-amd64.gz loglvl=all guest_loglvl=all</div><div>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</div> <div><br></div><div>and \
following additional configuration in domU config \
file.</div><div><br></div><div>----------------------------</div><div><br></div><div><div>pci=['06,04,0','08,01,0']</div><div><br></div>
<div><br></div><div>extra = 'swiotlb=force \
iommu=soft'</div><div><br></div></div><div>--------------------------</div><div><br></div><div>It \
was the syntax that was not right.</div><div><br></div><div>Thank you for your \
suggestion.</div> <div><br></div><div>Cheers,</div><div><br></div><div>Jignesh</div><div><br></div><div><br></div><br><div \
class="gmail_quote">On Mon, Sep 27, 2010 at 12:33 PM, Jignesh Patel <span \
dir="ltr"><<a href="mailto:j4sangoma@gmail.com">j4sangoma@gmail.com</a>></span> \
wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex;">Hi Todd,<div class="im"><br>1) lspci -vvv on the domU \
guest<br></div> ==><br># lspci -vvv<br>00:00.0 Ethernet controller: Realtek \
Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)<br> Subsystem: Realtek \
Semiconductor Co., Ltd. RT8139<br> Control: I/O+ Mem+ BusMaster+ SpecCycle- \
MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-<br>
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- \
<MAbort- >SERR- <PERR- INTx-<br> Latency: 32 (8000ns min, 16000ns \
max)<br> Interrupt: pin A routed to IRQ 22<br> Region 0: I/O ports at 1000 \
[size=256]<br>
Region 1: Memory at e2000000 (32-bit, non-prefetchable) [size=256]<br> \
Expansion ROM at e3400000 [disabled] [size=64K]<br> Capabilities: [50] Power \
Management version 2<br> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA \
PME(D0-,D1-,D2-,D3hot-,D3cold-)<br>
Status: D0 PME-Enable- DSel=0 DScale=0 PME-<br> Kernel driver in use: \
8139too<br> Kernel modules: 8139too, 8139cp<div class="im"><br><br><br> 2) the \
tail of the dmesg just after running the dhcp client (dhclient on \
debian)<br><br></div> I don't have dhcp client running on debian (dom0). The IP \
is provided by the gateway router.<br> On Gateway Router log I don't see DHCP \
request from domU when I use the Realtek card with pci passthrough.<br>
<br>From xenstore-ls :<br><br> pci = ""<br> 2 = ""<br> 0 \
= ""<br> domain = "sangomatest"<br> key-0 = \
"08:01.0"<br> vdevfn-0 = "100"<br>
uuid = "00ca7504-f956-8a08-4e0d-b67a526a16f3"<br> dev-0 = \
"0000:08:01.0"<br> frontend = \
"/local/domain/2/device/pci/0"<br> state = "4"<br> \
online = "1"<br>
frontend-id = "2"<br> uuid-0 = \
"089bc4f9-9e74-f7d7-32a4-54d164c1d9af"<br> num_devs = \
"1"<br> vdev-0 = "0000:00:00.00"<br> state-0 = \
"3"<br> root-0 = "0000:00"<br>
root_num = "1"<br><br><br><br>Could this be configuration issue ? \
<br><br><br>Thank you,<br><font \
color="#888888"><br>Jignesh<br><br><br><br></font><div class="gmail_quote"><div \
class="im">On Wed, Sep 22, 2010 at 9:49 PM, Todd Deshane <span dir="ltr"><<a \
href="mailto:deshantm@gmail.com" target="_blank">deshantm@gmail.com</a>></span> \
wrote:<br>
</div><div><div></div><div class="h5"><blockquote class="gmail_quote" \
style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt \
0.8ex;padding-left:1ex">Hi Jignesh,<br> <br>
Some requests for more info within.<br>
<div><br>
On Wed, Sep 22, 2010 at 6:21 PM, Jignesh Patel <<a \
href="mailto:j4sangoma@gmail.com" target="_blank">j4sangoma@gmail.com</a>> \
wrote:<br> > log files<br>
> ------------------------------------------------------------------<br>
> dom0 system log : <a href="http://pastebin.com/dm8zah43" \
target="_blank">http://pastebin.com/dm8zah43</a><br> > dom0 system info + lscpi -v \
: <a href="http://pastebin.com/24DjJczv" \
target="_blank">http://pastebin.com/24DjJczv</a><br> > Xen dmesg : <a \
href="http://pastebin.com/bkZSGsv7" \
target="_blank">http://pastebin.com/bkZSGsv7</a><br> > domU system log: <a \
href="http://pastebin.com/aHHur2m1" \
target="_blank">http://pastebin.com/aHHur2m1</a><br> > \
--------------------------------------------------------------------------------<br> \
><br> > Let me know if additional information is needed.<br>
<br>
</div>Could you also provide the following?<br>
<br>
1) lspci -vvv on the domU guest<br>
<br>
2) the tail of the dmesg just after running the dhcp client (dhclient on debian)<br>
<br>
You may also want to do some reading on threads related to xenstore-ls and pci<br>
<br>
See for example: <a href="http://xen.markmail.org/search/?q=xenstore-ls+pci" \
target="_blank">http://xen.markmail.org/search/?q=xenstore-ls+pci</a><br> <br>
You may be able to provide more information on specifically what is<br>
being created for the device in xenstore. I don't know the specifics,<br>
but those threads might help or give debugging tips.<br>
<br>
Hope that helps.<br>
<br>
Thanks,<br>
Todd<br>
<font color="#888888"><br>
--<br>
Todd Deshane<br>
<a href="http://todddeshane.net" target="_blank">http://todddeshane.net</a><br>
<a href="http://runningxen.com" target="_blank">http://runningxen.com</a><br>
</font></blockquote></div></div></div><br>
</blockquote></div><br></div>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic