buw20031220@bayern-mail.de
2006-May-31 20:46 UTC
[Xen-users] pcifront pci-0: pciback not responding (tg3)
Hello,
I am desperately trying to get pci-passthrough to working.
I want to pass a tg3 nic to domU.
when booting domU I get a lot of messages:
pcifront pci-0: pciback not responding!!!
in domU, "ifconfig eth... adress up"
hangs for 2 minutes, finally ifconfig -a shows a
correct setting with no data transmitted rx/tx
The IP Adress is being assigned, but there is no data
transmission possible on this interface (ping ..)
lspci in domU also hangs for 2 minutes, then reports
the device correctly.
When not doing pci passthrough, I can use the interface in dom0
just as usual.
I have also tried the other PCI devices - same result.
vif works, but I am afraid it is too slow for a real server.
Any Ideas ?
Thanks in advance
Winfried
My configuration:
================xen-dbg-3.0.2_09668-0.1.gz from SuSE,
suse xen kernel vmlinuz-2.6.16.16-1.4-xen based self compile
I have pciback compiled into the kernel. Later I also compiled
tg3 into the kernel, but it didn''t help.
The pciback hide and permissive seem to be correct.
More Error messages:
===================
domU, dmesg shows:
:
pcifront pci-0: pciback not responding!!!
pcifront pci-0: pciback not responding!!!
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
in dom0, xm dmesg shows:
(XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space
00000000
(XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space
000000c0
(XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space
0000009f
pciback runs with trace, so dom0 dmesg shows:
:
pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 0
pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340cc
pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 0
pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340d0
pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 27bdffe0
pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340dc
:
pciback: 0000:05:02.0: read 1 bytes at 0x59 = 0
pciback: 0000:05:02.0: read 4 bytes at 0x0
pciback: 0000:05:02.0: read 4 bytes at 0x0 = 16c714e4
pciback: 0000:05:02.0: read 4 bytes at 0x4
:
My config files:
===============
dom0:/boot/grub/menu.lst :
title Xen Debug buw --
root (hd0,5)
kernel /boot/xen-dbg.gz dom0_mem=384M
module /boot/vmlinuz-xen_buw root=/dev/cciss/c0d0p6 vga=0x314
splash=silent showopts pciback.permissive=Y
pciback.hide=(02:02.1)(05:01.0)(05:02.0)
module /boot/initrd-xen_buw
The domain config, nothing special except for:
dom0:/etc/xen/xmdom1buw00
pci = [ ''05,02,0'' ]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Glen Davis
2006-May-31 22:00 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
Not sure what is happening there, but I was able to get this to work using
SLES10, RC1 (using instructions below). Maybe someone else will know something
about your specific configuration.
Load the pciback module by typing -> modprobe pciback
Get the PCI ID for the hardware you will be using by typing - > lspci
IE * You may see 0000:02:06.0 for an e100 card.
Unbind the desired device intended for pciback. Go to /sys/bus/drivers and look
for the folder with your driver, for example e100. Go in the folder and you will
see the sym link for the device starting with your pci_id. Next ->
echo -n 0000:02:06.0 > /sys/bus/pci/drivers/e100/unbind
Now that sym link you just checked out should be gone.
Now bind the device to pciback.
echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/bind
Go to the pciback directory and you should see a new sym link created.
Now configure your Virtual Machine (DomU) to use the device.
Add to your conf file -> pci=[''0000:02:06.0'']
or
Specify it when loading your domU -> xm create -c vm1 pci=0000:02:06.0
>>> On 5/31/2006 at 2:46 PM, in message
<1149108363.447e008ba7d56@webmail.mnet-online.de>,
<buw20031220@bayern-mail.de> wrote:
Hello,
I am desperately trying to get pci-passthrough to working.
I want to pass a tg3 nic to domU.
when booting domU I get a lot of messages:
pcifront pci-0: pciback not responding!!!
in domU, "ifconfig eth... adress up"
hangs for 2 minutes, finally ifconfig -a shows a
correct setting with no data transmitted rx/tx
The IP Adress is being assigned, but there is no data
transmission possible on this interface (ping ..)
lspci in domU also hangs for 2 minutes, then reports
the device correctly.
When not doing pci passthrough, I can use the interface in dom0
just as usual.
I have also tried the other PCI devices - same result.
vif works, but I am afraid it is too slow for a real server.
Any Ideas ?
Thanks in advance
Winfried
My configuration:
================xen-dbg-3.0.2_09668-0.1.gz from SuSE,
suse xen kernel vmlinuz-2.6.16.16-1.4-xen based self compile
I have pciback compiled into the kernel. Later I also compiled
tg3 into the kernel, but it didn''t help.
The pciback hide and permissive seem to be correct.
More Error messages:
===================
domU, dmesg shows:
:
pcifront pci-0: pciback not responding!!!
pcifront pci-0: pciback not responding!!!
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
in dom0, xm dmesg shows:
(XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space
00000000
(XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space
000000c0
(XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space
0000009f
pciback runs with trace, so dom0 dmesg shows:
:
pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 0
pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340cc
pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 0
pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340d0
pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 27bdffe0
pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340dc
:
pciback: 0000:05:02.0: read 1 bytes at 0x59 = 0
pciback: 0000:05:02.0: read 4 bytes at 0x0
pciback: 0000:05:02.0: read 4 bytes at 0x0 = 16c714e4
pciback: 0000:05:02.0: read 4 bytes at 0x4
:
My config files:
===============
dom0:/boot/grub/menu.lst :
title Xen Debug buw --
root (hd0,5)
kernel /boot/xen-dbg.gz dom0_mem=384M
module /boot/vmlinuz-xen_buw root=/dev/cciss/c0d0p6 vga=0x314
splash=silent showopts pciback.permissive=Y
pciback.hide=(02:02.1)(05:01.0)(05:02.0)
module /boot/initrd-xen_buw
The domain config, nothing special except for:
dom0:/etc/xen/xmdom1buw00
pci = [ ''05,02,0'' ]
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
buw20031220@bayern-mail.de
2006-May-31 22:24 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
Thanks for the prompt reply, I am currently running SuSE10.1 as dom0, maybe I should switch to SLES10 RCx.> > Not sure what is happening there, but I was able to get this to work using > SLES10, RC1 (using instructions below). Maybe someone else will know > something about your specific configuration. > > > Load the pciback module by typing -> modprobe pciback > > Get the PCI ID for the hardware you will be using by typing - > lspci > > IE * You may see 0000:02:06.0 for an e100 card. > > > > > Unbind the desired device intended for pciback. Go to /sys/bus/drivers and > look for the folder with your driver, for example e100. Go in the folder and > you will see the sym link for the device starting with your pci_id. Next -> > echo -n 0000:02:06.0 > /sys/bus/pci/drivers/e100/unbind > Now that sym link you just checked out should be gone. > > Now bind the device to pciback. > echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/new_slot > echo -n 0000:02:06.0 > /sys/bus/pci/drivers/pciback/bind > Go to the pciback directory and you should see a new sym link created. > > Now configure your Virtual Machine (DomU) to use the device. > Add to your conf file -> pci=[''0000:02:06.0''] > or > Specify it when loading your domU -> xm create -c vm1 pci=0000:02:06.0 > > > >>> On 5/31/2006 at 2:46 PM, in message > <1149108363.447e008ba7d56@webmail.mnet-online.de>, > <buw20031220@bayern-mail.de> wrote: > Hello, > I am desperately trying to get pci-passthrough to working. > I want to pass a tg3 nic to domU. > > when booting domU I get a lot of messages: > pcifront pci-0: pciback not responding!!! > > in domU, "ifconfig eth... adress up" > hangs for 2 minutes, finally ifconfig -a shows a > correct setting with no data transmitted rx/tx > The IP Adress is being assigned, but there is no data > transmission possible on this interface (ping ..) > > lspci in domU also hangs for 2 minutes, then reports > the device correctly. > > When not doing pci passthrough, I can use the interface in dom0 > just as usual. > I have also tried the other PCI devices - same result. > > vif works, but I am afraid it is too slow for a real server. > > Any Ideas ? > Thanks in advance > Winfried > > > > My configuration: > ================> xen-dbg-3.0.2_09668-0.1.gz from SuSE, > suse xen kernel vmlinuz-2.6.16.16-1.4-xen based self compile > > I have pciback compiled into the kernel. Later I also compiled > tg3 into the kernel, but it didn''t help. > The pciback hide and permissive seem to be correct. > > > More Error messages: > ===================> > domU, dmesg shows: > : > pcifront pci-0: pciback not responding!!! > pcifront pci-0: pciback not responding!!! > NET: Registered protocol family 10 > lo: Disabled Privacy Extensions > ADDRCONF(NETDEV_UP): eth0: link is not ready > > > in dom0, xm dmesg shows: > > (XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space > 00000000 > (XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space > 000000c0 > (XEN) DOM6: (file=mm.c, line=486) Non-privileged attempt to map I/O space > 0000009f > > > pciback runs with trace, so dom0 dmesg shows: > : > pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 0 > pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340cc > pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 0 > pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340d0 > pciback: 0000:05:02.0: write request 4 bytes at 0x80 = 27bdffe0 > pciback: 0000:05:02.0: write request 4 bytes at 0x78 = 340dc > : > pciback: 0000:05:02.0: read 1 bytes at 0x59 = 0 > pciback: 0000:05:02.0: read 4 bytes at 0x0 > pciback: 0000:05:02.0: read 4 bytes at 0x0 = 16c714e4 > pciback: 0000:05:02.0: read 4 bytes at 0x4 > : > > My config files: > ===============> > dom0:/boot/grub/menu.lst : > > title Xen Debug buw -- > root (hd0,5) > kernel /boot/xen-dbg.gz dom0_mem=384M > module /boot/vmlinuz-xen_buw root=/dev/cciss/c0d0p6 vga=0x314 > splash=silent showopts pciback.permissive=Y > pciback.hide=(02:02.1)(05:01.0)(05:02.0) > module /boot/initrd-xen_buw > > The domain config, nothing special except for: > dom0:/etc/xen/xmdom1buw00 > pci = [ ''05,02,0'' ] > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
buw20031220@bayern-mail.de
2006-Jun-01 08:43 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
Zitat von buw20031220@bayern-mail.de:> Hello, > I am desperately trying to get pci-passthrough to working. > I want to pass a tg3 nic to domU. >.. I have browsed to this mailing list, there seems to be more users that do not get x86_64 and pci passthrough to working. In the devel-mailinglist, they seem to be working on x86_64 and things like dma ... We should be aware, that x86_64 came with xen 3.0 and pci passthrough came with xen 3.0.2 , but probably working for 32Bit, only. So my conclusion is for the moment ( 1.6.2006 ) : In Xen, x86_64 and pci passthrough is not yet working. Regards Winfried _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Glen Davis
2006-Jun-01 16:43 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
It is working for me on SLES10 RC2 x86_64, using the config in my previous post, I know this was busted in some earlier betas though.>>> <buw20031220@bayern-mail.de> 06/01/06 2:43 am >>>Zitat von buw20031220@bayern- mail.de:> Hello, > I am desperately trying to get pci- passthrough to working. > I want to pass a tg3 nic to domU. >.. I have browsed to this mailing list, there seems to be more users that do not get x86_64 and pci passthrough to working. In the devel- mailinglist, they seem to be working on x86_64 and things like dma ... We should be aware, that x86_64 came with xen 3.0 and pci passthrough came with xen 3.0.2 , but probably working for 32Bit, only. So my conclusion is for the moment ( 1.6.2006 ) : In Xen, x86_64 and pci passthrough is not yet working. Regards Winfried _______________________________________________ Xen- users mailing list Xen- users@lists.xensource.com http://lists.xensource.com/xen- users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
buw20031220@bayern-mail.de
2006-Jun-01 23:30 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
> It is working for me on SLES10 RC2 x86_64, using the config in my > previous post, I know this was busted in some earlier betas though. >good to hear this. I just downloaded SLES10 xen build 9697 and the problem has slightly, changed. If a Network is specified in domU /etc/sysconfig/network/ifcfg-eth-id-00\:... domU hangs in the boot. domU dmesg: pcifront pci-0: pciback not responding!!! tg3.c:v3.49 (Feb 2, 2006) pcifront pci-0: pciback not responding!!! pcifront pci-0: pciback not responding!!! PCI: Enabling device 0000:00:00.1 (0000 -> 0002) pcifront pci-0: pciback not responding!!! pcifront pci-0: pciback not responding!!! pcifront pci-0: pciback not responding!!! pcifront pci-0: pciback not responding!!! PCI: Setting latency timer of device 0000:00:00.1 to 64 pcifront pci-0: pciback not responding!!! pcifront pci-0: pciback not responding!!! tg3: Cannot find PowerManagement capability, aborting. pcifront pci-0: pciback not responding!!! tg3: probe of 0000:00:00.1 failed with error -5 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx SCSI subsystem initialized Driver ''sd'' needs updating - please use bus_type methods st: Version 20050830, fixed bufsize 32768, s/g segs 256 tg3.c:v3.49 (Feb 2, 2006) eth0: Tigon3 [partno(349321-001) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:17:08:4c:fe:f5 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth0: dma_rwctrl[769f4000] dma_mask[64-bit] pcifront pci-0: pciback not responding!!! pcifront pci-0: pciback not responding!!! dom0 boot parameter "pci=noacpi" won''t help here, in this case the system won''t boot at all. So is it a problem specific to the Networking card ? Using bnx2 instead does not work at all. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Glen Davis
2006-Jun-02 20:42 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
I just duplicated your pci not responding error. I seem to hit it only if I have my domU configured to use 4 processors. If I use less than that my nic is up and working just fine. I''ll file a bug against SLES10. Does yours work if you use 1 proc? Thanks, Glen>>> <buw20031220@bayern-mail.de> 06/01/06 5:30 pm >>>> It is working for me on SLES10 RC2 x86_64, using the config in my > previous post, I know this was busted in some earlier betas though. >good to hear this. I just downloaded SLES10 xen build 9697 and the problem has slightly, changed. If a Network is specified in domU /etc/sysconfig/network/ifcfg- eth- id- 00\:... domU hangs in the boot. domU dmesg: pcifront pci- 0: pciback not responding!!! tg3.c:v3.49 (Feb 2, 2006) pcifront pci- 0: pciback not responding!!! pcifront pci- 0: pciback not responding!!! PCI: Enabling device 0000:00:00.1 (0000 - > 0002) pcifront pci- 0: pciback not responding!!! pcifront pci- 0: pciback not responding!!! pcifront pci- 0: pciback not responding!!! pcifront pci- 0: pciback not responding!!! PCI: Setting latency timer of device 0000:00:00.1 to 64 pcifront pci- 0: pciback not responding!!! pcifront pci- 0: pciback not responding!!! tg3: Cannot find PowerManagement capability, aborting. pcifront pci- 0: pciback not responding!!! tg3: probe of 0000:00:00.1 failed with error - 5 Uniform Multi- Platform E- IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx SCSI subsystem initialized Driver ''sd'' needs updating - please use bus_type methods st: Version 20050830, fixed bufsize 32768, s/g segs 256 tg3.c:v3.49 (Feb 2, 2006) eth0: Tigon3 [partno(349321- 001) rev 2100 PHY(5704)] (PCIX:100MHz:64- bit) 10/100/1000BaseT Ethernet 00:17:08:4c:fe:f5 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth0: dma_rwctrl[769f4000] dma_mask[64- bit] pcifront pci- 0: pciback not responding!!! pcifront pci- 0: pciback not responding!!! dom0 boot parameter "pci=noacpi" won''t help here, in this case the system won''t boot at all. So is it a problem specific to the Networking card ? Using bnx2 instead does not work at all. _______________________________________________ Xen- users mailing list Xen- users@lists.xensource.com http://lists.xensource.com/xen- users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
buw20031220@bayern-mail.de
2006-Jun-04 22:36 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
Good to hear this, I never tried anything else but 4 processors. I will try this within the next 24 hours - the server should go into "production" soon and therefore I do not have so much time to play around with it. If you have a bugid or something, please post it here so i can check for the fix from time to time. As a compensation for the problem I have started to run Xen/HVM with Windows XP on an Acer Notebook "Aspire 5653" and it is running fine. I''m a bit xen-mad at the moment. http://en.opensuse.org/Xen_Full_Virtualization_Example is a perfect point to start. Best Regards Winfried> I just duplicated your pci not responding error. I seem to hit it only > if I have my domU configured to use 4 processors. If I use less than > that my nic is up and working just fine. I''ll file a bug against > SLES10. Does yours work if you use 1 proc? >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
buw20031220@bayern-mail.de
2006-Jun-05 21:40 UTC
Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
> I just duplicated your pci not responding error. I seem to hit it only > if I have my domU configured to use 4 processors. If I use less than > that my nic is up and working just fine. I''ll file a bug against > SLES10. Does yours work if you use 1 proc? > >I just edited domU config for having 1 real and 1 virtual cpu, but the result was similar as before: (2.6.16.18-1.6-xen, xen-3.0.2_09697-0.1 ) : INIT: Entering runlevel: 5 Boot logging started on /dev/tty1(/dev/console) at Mon Jun 5 23:31:02 2006 Master Resource Control: previous runlevel: N, switching to runlevel:5 Hotplug is already active (disable with NOHOTPLUG=1 at the boot prodone Initializing random number generator done Starting irqbalance failed coldplug scanning input: * done scanning pci: * done scanning usb: usbcore: registered new driver usbfs usbcore: registered new driver hub done . . . . . . . . . . . . . . . . . . . . done . . Setting up network interfaces: lo lo IP address: 127.0.0.1/8 done Waiting for mandatory devices: eth-id-00:17:08:4c:fe:f5 20 19 18 17 15 tg3.c:v3.49 (Feb 2, 2006) PCI: Enabling device 0000:00:00.1 (0000 -> 0002) eth0: Tigon3 [partno(349321-001) rev 2100 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:17:08:4c:fe:f5 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth0: dma_rwctrl[769f4000] dma_mask[64-bit] eth0 device: Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet (rev 10) eth0 configuration: eth-id-00:17:08:4c:fe:f5 eth0 IP address: XXXXXXXXXXXX/16 done Setting up service network . . . . . . . . . . . . . . done. Starting syslog services done Starting resource manager done Starting RPC portmap daemon done Importing Net File System (NFS) unused Starting nfsboot (sm-notify) done Starting SSH daemon done Starting cupsd done NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth0: link is not ready IPv6 over IPv4 tunneling driver sit0: Disabled Privacy Extensions Starting ypbind . . . . : _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
buw20031220@bayern-mail.de wrote:> Hello, > I am desperately trying to get pci-passthrough to working. > I want to pass a tg3 nic to domU. > > when booting domU I get a lot of messages: > pcifront pci-0: pciback not responding!!!If I understand your issue correctly I believe the following should at least provide some explanation for the behavior you''re experiencing. All tg3 devices are a bit quirky and need extra handling to work with Xen. Specifically, they require that certain non-standard parts of their PCI configuration space be writable. Try using a recent version of xen-unstable, which should have a patch that alleviates the problem you''re having, but be warned the fix leaves something to be desired from a security perspective. There is in-progress work on the pciback driver to address the security concerns of the current fix. Stay tuned to the xen-devel list if interested. If the problem persists on the newest xen-unstable please post a description of the problem to xen-devel for greater visibility. Cheers -Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users