I am using UEFI, yes. I found the issue. I don't believe SmartOS is
sending an ACPI signal when the host shuts down. The current way
SmartOS shuts down zones is not compatible with bhyve zones. There is
an alternate method of shutting down bhyve zones that happens, and
it is clear that OpenBSD (and maybe others) does not like this method
of shutting down. The issue is raised on the mailing list, so maybe
a solution will be found and implemented.
On 7/18/25 3:31 PM, Lloyd wrote:
Courtney wrote:
I watched for shutdown events and it seems OpenBSD is not receiving ACPI
signals. I looked at my other OpenBSD guests, they also are not
receiving these ACPI signals and are not shutting down cleanly. I will
have to investigate again to see if my Linux VMs are receiving these
signals or not. What I see is my other OpenBSD VMs recover just fine,
but my one VM needs an fsck due to an sqlite file. My assumption is that
OpenBSD is doing what it should, but bhyve is not sending the signal,
for whatever reason. I have the right flags set (the defaults) in
OpenBSD to respond to ACPI signals properly.
FWIW, Hyper-V and VMware shut down OpenBSD cleanly, but it does so in
response to requests from vmt(4) or hyperv(4), not ACPI.
Are you booting OpenBSD via UEFI?
