words:
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: quentin.thebault@defenso.fr
X-Bugzilla-Status: New
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: virtualization@FreeBSD.org
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID:
In-Reply-To:
References:
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
List-Id: Discussion
List-Archive: https://lists.freebsd.org/archives/freebsd-virtualization
List-Help:
List-Post:
List-Subscribe:
List-Unsubscribe:
X-BeenThere: freebsd-virtualization@freebsd.org
Sender: owner-freebsd-virtualization@FreeBSD.org
MIME-Version: 1.0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283215
--- Comment #2 from Quentin Th=C3=A9bault ---
New test with OpenBSD 7.6 guest on 15.0-RELEASE bhyve host.
No crash. The device is found and the driver (qwx) loads during boot. The
interface is created but cannot be brought up.
The following comes up in `dmesg` / when doing `ifconfig qwx0 up`.
```
qwx0: failed to receive control response completion, polling...
qwx0: Service connect timeout
qwx0: failed to connect to HTT: 35
qwx0: failed to start core: 35
qwx0: fatal firmware error
qwx0: fatal firmware error
```
Note: I confirm the OpenBSD qwx driver does work with that hardware when bo=
oted
baremetal.
--=20
You are receiving this mail because:
You are the assignee for the bug.=