Xen project Mailing List

Re: [Xen-devel] Xen >4.10 bricks onboard NIC of Dell Optiplex 7060

From: "Bell, Oren" <oren.bell@xxxxxxxxx>

Date: Wed, 30 Oct 2019 18:24:30 +0000

Accept-language: en-US

Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wustl.edu; dmarc=pass action=none header.from=wustl.edu; dkim=pass header.d=wustl.edu; arc=none

Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=8mvW5yiQFQtGEJp1oa3kQjeGJOwOhiElrf4CTGKOb/o=; b=FbwPWEIshRAWT9v+dA1TkfjnQ6seJ7U0284bdRdO3rRjxHcbeqv6uH8qddK8bRIxaA3tDFFUUei87zn3SQ4JySrOJ++NNQoqqZkcj+PVDn0b1hzCQwdxSbMGFI+yaMkthykiCQcy00ZHOmLunh8jeTnDrDULurNhhuvP0YSW/5YH1l287ZTOKu2AfcQg4JjbivTc9bsKh8VlyIByC0MiZFNoKXph02s2iq2ROmj4xTPGx1Wb5dMSc7wHX2Wz5aq0rJUTCG+bE4shemNyirvitFMRJIpGSNuGQ+omUYVEzisjvn5wY1a0b1re5A5F68ts+W7iiXAtXSemeJm+AdeiXg==

Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=X4dvffN7cNh/TETeTYWPudjf800sQpGkuO5rdKXJPzLRonnufKofvh2EztyFbND9loHhGJpzgRQi3hAodjhPGuvroNdCHcXRAcdl2o4LVlheWDiWyNE/kozRYe+UCkoY+5avkbPhzsc8I73HNhXI1HV/suTAOAuMtjCsTUm/DSsBowIJOaAMkQd6DQHl6N+kLIJF0NVqsejgvmobwhd8upMI0aSPjK/SkQiRJWVHx+BLnet4DrhJBmr6mbS07R1hIaH7Klb3W9MUJnUAXRTVRQyTAcgWCMvOXVuAkEIe7Diz+5p/d66zK5I2MZAytFeVbwZ+DB3QpFHTJ6IXor+CRg==

Authentication-results: spf=none (sender IP is ) smtp.mailfrom=oren.bell@xxxxxxxxx;

Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>

Delivery-date: Wed, 30 Oct 2019 18:24:35 +0000

List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Thread-index: AQHVjN9Jz8ZYVdlqdkGT46MhTzcVOqdvw34AgAO/fwk=

Thread-topic: [Xen-devel] Xen >4.10 bricks onboard NIC of Dell Optiplex 7060

Running Xen Dom0-less leaves the NIC intact, so you're correct in assessing that Xen by itself is not the cause.

As for running without the driver, I'm not sure that's possible (at least for my competency). It uses the Intel Base Gigabit driver that's built into the kernel.

And running the machine without using the NIC will still break it.

As for the IOMMU suggestion: we still got basic pinging to work, assuming an IP address was statically allocated, so I don't think IOMMU is a valid route for investigation, as any aberrations there should leave the NIC totally non-functional.

From: Jan Beulich <jbeulich@xxxxxxxx>
Sent: Monday, October 28, 2019 4:03 AM
To: Bell, Oren <oren.bell@xxxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx <xen-devel@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen >4.10 bricks onboard NIC of Dell Optiplex 7060

On 27.10.2019 17:09, Bell, Oren wrote:
> I've encountered an issue where installing Xen >4.10 on a Dell Optiplex will break the onboard NIC. This issue persists if the computer is booted without Xen, after OS reinstall, and even if removing the SSD and HDD completely to boot from a LiveUSB. The only way to fix the issue is to install Windows 10 on the machine. This appears to "fix" the firmware of the NIC. After reinstalling Ubuntu, the NIC continues to work (until Xen is installed again).
>
> This bug was confirmed with both Xen 4.10 and 4.12 installed on Ubuntu 18.04.
>
> If this is a known issue, is there some "in-work patch" I can be pointed to?

This is a rather strange problem you're facing - Xen itself doesn't
do anything to NICs. Therefore I'm afraid some more experimenting
may be needed to somehow narrow where things go wrong. In particular
I'd be curious to understand whether it's indeed Xen that breaks
things, or whether e.g. other software misbehaves if run on top of
Xen. As a first step, could you boot
- Xen without a Dom0 kernel,
- Xen with a Dom0 kernel, but without a driver for the NIC,
- Xen with a Dom0 kernel and with a driver for the NIC, but without
actually configuring/using the NIC?
Could you further check whether Xen using the presumably present
IOMMU matters? (Providing maximum verbosity hypervisor and kernel
logs would of course also help, in particular e.g. to know whether
there is an IOMMU in the system, and also to see whether any
anomalies get logged.)

Jan

_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel