[Bug 254458] emulators/virtualbox-ose saved states of running FreeBSD or FreeBSD-based guests are almost completely non-responsive after starting; ACPI shutdowns fail

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254458

Graham Perrin <grahamperrin at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |grahamperrin at gmail.com,
                   |                            |madpilot at FreeBSD.org
            Summary|emulators/virtualbox-ose    |emulators/virtualbox-ose
                   |some versions of FreeBSD do |saved states of running
                   |not work, if started from a |FreeBSD or FreeBSD-based
                   |snapshot that was saved     |guests are almost
                   |whilst the working FreeBSD  |completely non-responsive
                   |guest ran                   |after starting; ACPI
                   |                            |shutdowns fail

--- Comment #13 from Graham Perrin <grahamperrin at gmail.com> ---
In nearly all affected cases: 

*   the guest seems to be _completely_ non-responsive to 
    mouse and keyboard input after starting from the saved state. 

----

<https://photos.app.goo.gl/rLTF4nrueco8wTGR7> is a rare example of a guest that
_did_ briefly respond (soon after the start from the saved state) to Control-F1
or Control-F2 (equivalent to Control-Alt-F1 or Control-Alt-F2 with real
hardware):

*   I got a TTY, but then
*   no further response to Control-F1, Control-F2 or Control-F9
*   ACPI shutdown failed. 

Guest: 

*   clean installation of GhostBSD
*   based on FreeBSD 13.0-STABLE
*   guest additions 6.1.18 integral to the installation
*   recently released GhostBSD-21.04.27.iso from 
    <https://www.ghostbsd.org/download>.


Host: 

% pkg query '%o %v %R' virtualbox-ose virtualbox-ose-kmod
emulators/virtualbox-ose 6.1.20 FreeBSD
emulators/virtualbox-ose-kmod 6.1.20 FreeBSD
% uname -v
FreeBSD 14.0-CURRENT #93 main-n246330-5eb9c93a20d: Tue Apr 27 05:14:26 BST 2021
    root at mowa219-gjp4-8570p:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG 
% 

----

To Guido Falsi: my apologies, this bug report is somewhat messy. The 'kern'
assumption was misguided, and so on. 

If, for a moment, we _ignore_ the long steps to reproduce at comment 5 …

… is there enough for this to be recognisably an (emulators/virtualbox-ose)
issue with VirtualBox 6.⋯ on some FreeBSD hosts? 

----

I have no comparable problem with a FreeBSD 13.0-RELEASE guest on a Windows 10
20H2 host. 

I can not recall anything like this bug with 5.2.44_4 as the host on -CURRENT. 

I'm now installing emulators/virtualbox-ose 6.1.20 and
emulators/virtualbox-ose-kmod 6.1.20 on a FreeBSD 13.0-RELEASE host, to tell
whether the bug is reproducible (for me) without 14.0-CURRENT.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.