WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] pcifront pci-0: pciback not responding (tg3)
From: buw20031220@xxxxxxxxxxxxxx
Date: Thu, 01 Jun 2006 00:24:54 +0200
Delivery-date: Wed, 31 May 2006 15:25:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <447DBD3F.DBD5.0021.0@xxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1149108363.447e008ba7d56@xxxxxxxxxxxxxxxxxxxxxx> <447DBD3F.DBD5.0021.0@xxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Internet Messaging Program (IMP) 3.0
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@xxxxxxxxxxxxxxxxxxxxxx>,
> <buw20031220@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx 
> http://lists.xensource.com/xen-users
> 



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>