On 9/23/25 10:59, Matt Churchyard wrote:
Bhyve is designed to trap a kill (term) signal and trigger acpi poweroff, so this is the documented and intended way to power off a guestFrom the man page: SIGNAL HANDLING bhyve deals with the following signals: SIGTERM Trigger ACPI poweroff for a VM This definitely works and is completely reliable with most guests. Vm-bhyve sends it twice as this seemed to get Windows to respond to the request much more consistently and it would often appear to completely ignore a single kill command. I don't know why this is the case though or whether other hypervisors do something different when requesting a shutdown compared to what bhyve does. Simply triggering acpi poweroff "should" be enough.
I can just guess about this. When I press a power button on a desktop with Windows 10, it just ends screensaver (well, blank screen, to be precise), so I have to press it another time to actually turn it off. It does sound like a similar "issue".
Regards, meka
