Xen devel - Dec 2008 - error enable msi for guest 4 status fffffff0 (link of nic exposed directly to domU using pciback stays down)

Hi xen-devel,

I have been trying to pcihide a NIC from dom0 and directly claim it on domU.
The dom0 had come up with the bnx2 driver claiming the nic card, but after
that i did an unbind and bound the pciback driver with this interface.

lspci on domU shows the only pci device and it is claimed by the bnx2
driver.However the link of the interface as shown by ethtool continues to be
down.

When i tried to run ifconfig on the interface in DomU, it threw the
following error.
*#ifconfig eth1 192.168.23.2 netmask  255.255.255.0
pci frontend enable msi failed for dev 0:0
SIOCSIFFLAGS: Function not implemented
*
The following info was logged on the dmesg of DomU
*lo: Disabled Privacy Extensions
IPv6 over IPv4 tunneling driver
pci frontend enable msi failed for dev 0:0
*

Dmesg logs on Dom0 gives the following error...
*device vif4.0 entered promiscuous mode
eth0: port 2(vif4.0) entering learning state
eth0: topology change detected, propagating
eth0: port 2(vif4.0) entering forwarding state
blkback: ring-ref 9, event-channel 11, protocol 1 (x86_32-abi)
blkback: ring-ref 10, event-channel 12, protocol 1 (x86_32-abi)
vif4.0: no IPv6 routers present
PCI: Enabling device 0000:05:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 17 (level, low) -> IRQ 17
get owner for dev 0 get 4
error enable msi for guest 4 status fffffff0*

I am amazed that nobody else has hit this issue before. Appreciate if
anybody can throw some light on this.

Regards,
Karthik


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