Some more info, if it helps
On DomU you get this following error messge
ifconfig eth0 192.168.23.2 netmask 255.255.255.0
pci frontend enable msi failed for dev 0:0
SIOCSIFFLAGS: Function not implemented
Dmesg logs on Dom0 give the following message...
PCI: Enabling device 0000:05:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 17 (level, low) -> IRQ 17
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
get owner for dev 0 get 4
error enable msi for guest 4 status fffffff0
On Wed, Dec 3, 2008 at 11:30 AM, xen rkar <xen.rkar@xxxxxxxxx> wrote:
> Hi Bastian,
> Thanks for that info. I have now been able to get the nic seen in the
> domU, however the link of the nic is reported as down.
> I get the following error on the screen " pci frontend enable msi
> failed for dev 0:0"
> I have connected this link on a cross-over connection to another
> system, the link on the other system shows it as up. So I am sure the
> link is up, but the DomU incorrectly shows it as down.
> Any idea on whats going wrong?
> On Tue, Dec 2, 2008 at 6:10 PM, Bastian Blank <bastian@xxxxxxxxxxxx> wrote:
>> On Tue, Dec 02, 2008 at 04:02:49PM +0530, xen rkar wrote:
>>> The pciback module is clearly available in the kernel/romdisk and i
>>> have passed the parameters to the kernel to ignore the pci-id.
>>> But I continue to see it listed when i run "lspci".
>> You missunderstand "hide". This definition hides it from the real driver
>> modules, not from the kernel at all.
>>> Have i missed any steps, appreciate if you kind give me any pointers
>>> on how to check if i'm doing the right steps and move forward.
>> Use the documentation and stop after you get an _error_.
>> Extreme feminine beauty is always disturbing.
>> -- Spock, "The Cloud Minders", stardate 5818.4
Xen-users mailing list