[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [BUG] problems with NICs pass through to OpenBSD guest


  • To: Adam Szewczyk <szewcson@xxxxxxxxx>
  • From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Date: Mon, 19 Sep 2022 11:21:17 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=LBk+G0ZMMyPoNS41TcAh9VbeoonGdwsm0J/JBubJNKU=; b=WKUmtty69ycVz0pJgUAYnXMz6odM5eufDwYfGZXm9h9aHucqwKe78XqUK9aZ+gQ2/joFjw9fTk2ZsdmzAXtijgR8E4YGEb1QjKgynGngRA/QtE37HzaK2bWQfpALQ+evLfQcJ8CKfVTkM8oMUyA4Xm2J3pV7c1+mbdQ6u9c8Ee7vj6Czpl4n6P76p+Jdxlj521v8JVeNknOyoLfJRSy2FNTnEhfWNOJ3tVt3RHl/Ncv80YX9oVD2UBIDRAdmZSPW/HGyUXmE7SLOE650XELIO0lAamHDeZW8TUwT9GXPoUsbEc1f+WU7p4N/k5EElW7JSrCt2N0oy7tkv7zqKYAlsw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PMRNa9hSY54MJl6GGF3rRmoImZQEz/teoHzO9K+WyLDmsfKXWEopO+V72gpFuSxiAFSnSYQnif79Qp0yQtFAJGgglPIDQEA4dhYJTrL8UveCsfEGkVT5gTTkKGjZ2UG6DKfl2oDs0BOv+9ZyJOc2Fb5Sa6t3XpShkkHiw+9ER9W9JTBWvSGSyuOV0hbA1nVrY4nq2xef/PEcI8Qv1yJGgfoevFhgbbuP9+QCGlbDac9yve9oRM7y3DsmPnECvWDybPAmtpp+EraLV+eRcURUz6OqZZNsxx+XA0kWzPc9BYwnYzVZ+KZnZSIMtKHrdqH5swKMYY2Ndsoom+D410Gz6g==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
  • Cc: xen-devel@xxxxxxxxxxxxx
  • Delivery-date: Mon, 19 Sep 2022 09:21:50 +0000
  • Ironport-data: A9a23:H5edo6s9Drh6z//DscLuVCLjVefnVFZfMUV32f8akzHdYApBsoF/q tZmKWzQOPjbajGmfox1aonnpE1VvJ/Tn9ZgHQZpqCEwHnsU+JbJXdiXEBz9bniYRiHhoOOLz Cm8hv3odp1coqr0/0/1WlTZhSAgk/vOHtIQMcacUghpXwhoVSw9vhxqnu89k+ZAjMOwRgiAo rsemeWGULOe82MyYzl8B56r8ks15qyj4WJA5zTSWNgQ1LPgvyhNZH4gDfnZw0vQGuF8AuO8T uDf+7C1lkuxE8AFU47Nfh7TKyXmc5aKVeS8oiM+t5uK23CukhcawKcjXMfwXG8M49m/c3Kd/ /0W3XC4YV9B0qQhA43xWTEAe811FfUuFLMqvRFTGCFcpqHLWyKE/hlgMK05FZME+cNxEGRAz vkVNQ03QkDEory6zL3uH4GAhux7RCXqFKU2nyg5iBv/XbMhS52FRLjW79hF2jt2ntpJAfvVe 8seb3xocQjEZBpMfFwQDfrSns/x3iW5L2Ie9QLT/PRni4TQ5FUZPLzFKt3ad8bMXcxItk2Zu njH7yLyBRRy2Nm3mWPfqS333r+ncSXTZ5wyD5+R/6dR22bN7UsMAzFLUVKAiKzs4qK5c5cFQ 6AOwQI1v6Ut/1esSPHyWhS5pDiPuRt0c8pdFag25R+AzoLQ4h2FHS4UQzgHb8Yp3PLaXhQv3 16N2tnvVTpmteTMTWrHr+nE6zSvJSISMGkOIzceShcI6MXip4d1iQ/TStFkE+i+idid9SzM/ g1mZRMW39075fPnHY3ilbwbq1pAfqT0czM=
  • Ironport-hdrordr: A9a23:J/8hgqv+SlZ2ukkgyRSxklTB7skCk4Mji2hC6mlwRA09TyXGra 2TdaUgvyMc1gx7ZJhBo7+90We7MBbhHLpOkPEs1NaZLXDbUQ6TQL2KgrGD/9SNIVycygcZ79 YaT0EcMqyNMbEZt7ec3ODQKb9Jrri6GeKT9IHjJh9WPHxXgspbnmNE42igYy9LrF4sP+tCKH PQ3LsxmxOQPVAsKuirDHgMWObO4/XNiZLdeBYDQzoq8hOHgz+E4KPzV0Hw5GZWbxp/hZMZtU TVmQ3w4auu99m91x/nzmfWq7BbgsHoxNdvDNGFzuIVNjLvoAC1Y5kJYcz1gBkF5MWUrHo6mt jFpBkte+x19nPqZ2mw5SDg3gHxuQxemUPK+Bu9uz/OsMb5TDU1B45qnoRCaCbU7EImoZVVzL 9L93jxjesbMTrw2ADGo/TYXRBjkUS55VA4l/QIsnBZWYwCLJdMsI0k+l9PGptoJlOx1GkeKp ggMCjg3ocZTbvDBEqp/1WHgebcFUjbJy32DnTr4aeuonhrdHMQ9Tpq+CVQpAZCyHsHceg02w 31CNUWqFhwdL5pUUtcPpZ1fSLlMB24fTv8dESvHH/AKIYrf1rwlr+f2sRE2AjtQu1B8KcP
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Fri, Sep 16, 2022 at 05:08:59PM +0200, Adam Szewczyk wrote:
> Sorry, I always forgot that default answer is "answer" to not "answer to
> all".
> 
> My xl dmesg after calling those debug-keys is:

Trimming the trace:

> (XEN) MSI information:

> (XEN)  MSI    125 vec=72 lowest  edge   assert  log lowest dest=00000100
> mask=0/  /?

> (XEN)  MSI    138 vec=62 lowest  edge   assert  log lowest dest=00000001
> mask=0/  /?
> (XEN)  MSI    139 vec=6a lowest  edge   assert  log lowest dest=00000010
> mask=0/  /?

> (XEN) IRQ information:

> (XEN)    IRQ: 125 vec:72 PCI-MSI         status=030 aff:{8}/{0-11}
> in-flight=0 d94:151(-M-)

> (XEN)    IRQ: 138 vec:62 PCI-MSI         status=030 aff:{0}/{0-11}
> in-flight=0 d92:151(---)
> (XEN)    IRQ: 139 vec:6a PCI-MSI         status=010 aff:{4}/{0-11}
> in-flight=0 d92:150(---)

Was domain with ID 94 your OpenBSD box? There's another domain with
passthrough devices (ID 92).

If your OpenBSD domain is the one with ID 94 it seems like the
interrupt source is masked, so no interrupts will be injected to the
guest.  That however might be just the response from the guest after
seeing that the interrupt source is not behaving correctly.

Are yuo using a debug hypervisor? If not it would be helpful to do so,
in order to maybe get more information on `xl dmesg`.

Can you also paste the QEMU log for the OpeNSD domain?  Those logs are
in /var/log/xen/qemu-dm-<domain name>.log, on most distros, not sure
if QubesOS puts them at the same place.

Regards, Roger.



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.