Page MenuHomeFreeBSD

bhyve: improve console error reporting on arm64
ClosedPublic

Authored by novel on Jan 4 2026, 2:14 PM.
Tags
None
Referenced Files
F168111564: D54504.diff
Wed, Aug 26, 10:51 AM
Unknown Object (File)
Tue, Aug 25, 9:27 PM
Unknown Object (File)
Tue, Aug 25, 4:52 AM
Unknown Object (File)
Sun, Aug 23, 7:28 AM
Unknown Object (File)
Sun, Aug 23, 5:03 AM
Unknown Object (File)
Fri, Aug 21, 4:46 AM
Unknown Object (File)
Thu, Aug 20, 1:43 PM
Unknown Object (File)
Wed, Aug 19, 2:16 AM

Details

Summary

Currently, on arm64, if bhyve fails to initialize the console,
it falls into assert(), which does not look particularly pretty
for users.

Replace the assert with proper error handling so bhyve prints
a meaningful error message and exits with status code 4 (error).
That matches the behavior on amd64.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

novel requested review of this revision.Jan 4 2026, 2:14 PM

Relatively simple way to trigger this error is to run kldunload nmdm and then run bhyve -c 1 -o bootrom=/usr/local/share/u-boot/u-boot-bhyve-arm64/u-boot.bin -o console=/dev/nmdmFoobarA test.

This revision is now accepted and ready to land.Jan 4 2026, 2:29 PM