| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
RE: [Xen-users] Intel Quad NIC made visible in guest -> system crash
Hi!
thanks for the reply.
On Di, 2009-06-09 at 11:38 +0000, Joseph L. Casale wrote:
> >we have two Intel Quad Nic 82576, PCI ID 8086:10E8 and use the igb
> >driver 1.3.19.3 on Debian 5.0.1.
> >
> >I used the pciback.hide XEN kernel parameter and made on of the NIC's
> >interfaces available in a DomU.
> >
> >Now, when I am starting the VM, the system crashes (log attached)
>
> W/o doing any research myself, I vaguely remember someone here having
> similar results and suggesting that some nics have a design such that
> some ports are tied together as a result of sharing components on the
> nic itself. Basically, you may have a nic that is really only two
> independent nics, each with two ports so you have to pass two in at
> once etc.
>
> A quick search or test should validate this...
I already blacklisted all 4 ports of the whole nic. Next I blacklisted
the igb module in dom0 as suggested in
http://lists.xensource.com/archives/html/xen-users/2007-10/msg00598.html
were Stephan Seitz recommends to not use the module in the dom0.
I also disabled MSI interrupts in the igb driver (make
CFLAGS_EXTRA=-DDISABLE_PCI_MSI install) as the igb readme says there
might be some problems.
Now, when starting the domU, I do not get the message anymore that IRQ
#17 was disabled, but still:
[ 623.361836] ACPI: PCI Interrupt 0000:10:00.1[B] -> GSI 17 (level,
low) -> IRQ 17
[ 623.362307] pciback 0000:10:00.1: Driver tried to write to a
read-only configuration space field at offset 0xa8, size 2. This may be
harmless, but if you have problems with your device:
[ 623.362310] 1) see permissive attribute in sysfs
[ 623.362311] 2) report problems to the xen-devel mailing list along
with details of your device obtained from lspci.
[ 623.362771] PCI: Setting latency timer of device 0000:10:00.1 to 64
When doing ifup eth0 inside the domU, I get the message that the cable
is not connected.
Platform is amd64 with 2 Intel Xeon CPUs with 4 cores.
On many places I read to use the boot option pciback.permissive -
unfortunately my kernel does not support that setting. I would have been
happy to avoid recompiling the kernel, and I read that pciback should
work without the permissive flag as well.
Any ideas? please ...
Best Regards,
Alexander
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home