Bug 247081 - bhyve: Upgrading to Debian guest from 9.x to 10.4 on FreeBSD 12.1p5 host causes IO failure
Summary: bhyve: Upgrading to Debian guest from 9.x to 10.4 on FreeBSD 12.1p5 host caus...
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bhyve (show other bugs)
Version: 12.1-RELEASE
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-virtualization (Nobody)
Keywords: needs-qa
Depends on:
Reported: 2020-06-08 10:17 UTC by Kurt Jaeger
Modified: 2020-07-09 04:25 UTC (History)
2 users (show)

See Also:
koobs: mfc-stable12+


Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Jaeger freebsd_committer 2020-06-08 10:17:25 UTC

Comment 1 Kurt Jaeger freebsd_committer 2020-06-08 10:19:51 UTC
Problem: debian 9.12 running on 12.1p5 as bhyve VM works.

Updating to 10.4 crashes shortly after boot with:

[   46.564639] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   46.565562] ata1.00: failed command: FLUSH CACHE EXT
[   46.566215] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 6
[   46.566215]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   46.567954] ata1.00: status: { DRDY }
[   46.894022] do_IRQ: 6.35 No irq handler for vector
[   51.927018] ata1.00: revalidation failed (errno=-5)
[   52.242964] do_IRQ: 6.35 No irq handler for vector

Any ideas on how to debug / fix ?
Comment 2 Peter Grehan freebsd_committer 2020-06-08 10:36:08 UTC
I'm reasonably certain this is the issue fixed by r360399, "Update the cached MSI state when any MSI capability register is written" and MFCd to 12-stable with r361041.
Comment 3 Kubilay Kocak freebsd_committer freebsd_triage 2020-06-09 02:48:38 UTC
@Kurt are you able to test a stable/12 snapshot to verify?
Comment 4 Kurt Jaeger freebsd_committer 2020-06-09 06:24:41 UTC
Not yet. It's a production system, so I'm still considering if it's OK to wait for 12.2 or to handle the STABLE build.
Comment 5 Kurt Jaeger freebsd_committer 2020-07-09 04:25:31 UTC
Is this bug fixed by