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-devel

[Xen-devel] error enable msi for guest 4 status fffffff0 (link of nic ex

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] error enable msi for guest 4 status fffffff0 (link of nic exposed directly to domU using pciback stays down)
From: "xen rkar" <xen.rkar@xxxxxxxxx>
Date: Thu, 4 Dec 2008 15:08:43 +0530
Delivery-date: Thu, 04 Dec 2008 01:39:11 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=hj07d8NUeU5GHu7PBiXwkgOZmKtzPvR5Skok4rbyuZ4=; b=JOLCzMxSNxXUlDGj+4asclaigABLKjA6sFWhGclbDyU5jzrNnSF9XGlUghW0DNGavS u2PLDgxGczFTtU4Zf0NcJG+cc5Z7QHEl/UN7rpomEYgWn8bF3jnIzEitUtQ+KwNjhNFS hTq1iIv+oF23XjpGbXHyFZa/oBbP+0InIrGn0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=rjFQLR+HI/AW35y97WSvcxnZpjblqqtIkmBfBrux8fkNLOWdyAOTYsoULwJ2pBD5FE 2HrOSZfZrG3l2jXEaTdALBDcyx9IZYy96V9J0d463NldHkHrrF8vIQxAfE4PbK3OsVNu PrzFG7Wz1UcKgwXDZXyS9YCNWiybXMSlTW+gY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] error enable msi for guest 4 status fffffff0 (link of nic exposed directly to domU using pciback stays down), xen rkar <=