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/
Home Products Support Community News


RE: [Xen-users] Intel Quad NIC made visible in guest -> system crash

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Intel Quad NIC made visible in guest -> system crash
From: Alexander Menk <alex.menk.lists2@xxxxxxxxxxxxxx>
Date: Tue, 09 Jun 2009 15:27:04 +0300
Delivery-date: Tue, 09 Jun 2009 05:29:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:in-reply-to :references:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; bh=zE+3UTKzTpmPyNW+u2Pb/pwYTGH7+BXWkiO4dMPBJHI=; b=k6hOhBK0AxhTq8hepI88mjqlB3S9vluZ9OJf9aZ4sLmou7GAZ6b1IBXB+dz5dpOPjj KsQeX1y0quewAPlHHcjJlHJSfwieDGEu8qyV97aa6EXs1u3q33+sazvVOBdmIuP2BA7Q CZOq5L8AUTCm++Eyt940dKrWBds6P5ohhQfPc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=subject:from:to:in-reply-to:references:content-type:date:message-id :mime-version:x-mailer:content-transfer-encoding; b=mL+s7RGW4WrRsuki8xyfuoe017hZmu8ikz5W/XshJLdGkWvqxkv/T1bL11Qg9/cyLr aRjCRjO26DcTT9k90lfCoybdbqVQffVJdsx7Pr+xnavKZXAcyP8ydduJvMt20U2OmoGK 2qHr9u+Z7qjY1+eJheDiwogOQOsgw0hT4URBE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <ABF9510930E1374BA4B4C61A01104FBD8D4BC4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <1244539974.4062.4.camel@xxxxxxxxxxxxxxxxxxxxxx> <ABF9510930E1374BA4B4C61A01104FBD8D4BC4@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

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


Xen-users mailing list