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

[Xen-users] pciback not working with linux domU


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Wong Louis <mylover01ca@xxxxxxxxx>
  • Date: Mon, 20 Nov 2006 05:52:22 -0500 (EST)
  • Delivery-date: Mon, 20 Nov 2006 02:52:46 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=AvLr6oD3TOD1kprhYxzf5QbBDMrOsdkHSLobw4jDQ5vtQGi5j/LTFL5TtN+wR/j36V95CupiJFWQicXZn3vWa05f3QhsakvMGwmoTlvS5DdXeyMEnFejvR2jCX/DNMWD2r8ZcmjznYnEL+vwDgPYe/fX6tOODlre78ax+jfTYFo=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I am using the latest xen unstable and trying to
install this

00:19.0 Ethernet controller: Intel Corporation 82562V
10/100 Network Connection (rev 02)

since xen uses 2.6.16.29 it does not support it yet,
someone said (on google) that 2.6.18.3 supports it. So
I want to boot 2.6.18.3 in domU and enable it with the
pciback thing.

my seize commands are:

echo -n 0000:00:19.0 >
/sys/bus/pci/drivers/pciback/new_slot
echo -n 0000:00:19.0 >
/sys/bus/pci/drivers/pciback/bind 

(results from dmesg)
pciback: wants to seize 0000:00:19.0
pciback 0000:00:19.0: probing...
pciback 0000:00:19.0: seizing device
pciback 0000:00:19.0: pcistub_device_alloc
pciback 0000:00:19.0: initializing...
pciback 0000:00:19.0: initializing config
pciback 0000:00:19.0: initializing virtual
configuration space
pciback 0000:00:19.0: added config field at offset
0x04
pciback 0000:00:19.0: added config field at offset
0x3c
pciback 0000:00:19.0: added config field at offset
0x3d
pciback 0000:00:19.0: added config field at offset
0x0c
pciback 0000:00:19.0: added config field at offset
0x0d
pciback 0000:00:19.0: added config field at offset
0x0f
pciback 0000:00:19.0: added config field at offset
0x10
pciback 0000:00:19.0: added config field at offset
0x14
pciback 0000:00:19.0: added config field at offset
0x18
pciback 0000:00:19.0: added config field at offset
0x1c
pciback 0000:00:19.0: added config field at offset
0x20
pciback 0000:00:19.0: added config field at offset
0x24
pciback 0000:00:19.0: added config field at offset
0x30
pciback 0000:00:19.0: Found capability 0x1 at 0xc8
pciback 0000:00:19.0: added config field at offset
0xc8
pciback 0000:00:19.0: added config field at offset
0xca
pciback 0000:00:19.0: added config field at offset
0xce
pciback 0000:00:19.0: added config field at offset
0xcf
pciback 0000:00:19.0: enabling device
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level,
low) -> IRQ 19
pciback 0000:00:19.0: reset device
ACPI: PCI interrupt for device 0000:00:19.0 disabled


---
I put pci=['0000:00:19.0'] in the hvm file, when it
boots it says:

pciback pci-1-0: allocated pdev @ 0xf2f72a40
pciback pci-1-0: getting be setup
pciback pci-1-0: exporting dom 0 bus 0 slot 19 func 0
pciback: vpci: 0000:00:19.0: assign to virtual slot 0
pciback pci-1-0: Publishing pci roots
pciback pci-1-0: writing root 0 at 0000:00
pciback pci-1-0: fe state changed 1


but inside the domU the lspci does not show the
device.


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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


 


Rackspace

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