[Bug 229824] Fatal trap 1 when resuming from S3 with a VirtualBox VM running

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Aug 8 18:10:34 UTC 2018


John Baldwin <jhb at FreeBSD.org> changed:

           What    |Removed                     |Added
                 CC|                            |jhb at FreeBSD.org

--- Comment #1 from John Baldwin <jhb at FreeBSD.org> ---
FreeBSD doesn't have a way to let external hypervisors like vbox work across
suspend and resume.  I did add a hook for bhyve in
https://svnweb.freebsd.org/base?view=revision&revision=259782.  We would need
something similar.  The same issue matters for permitting multiple hypervisors
being active at the same time (e.g. you can't run both bhyve and vbox at the
same time currently).  I had been thinking of adding a kind of hypervisor
framework to let hypervisors allocate the VMX region and then permit
associating it with a given process so that you could do the right vmxon/vmxoff
during context switch.  Having that would also allow us to more cleanly handle
suspend/resume for arbitrary hypervisors.

One thing you might be able to do for now is change the vbox driver to set the
same vmm_resume_p pointer that bhyve's vmm.ko sets during MOD_LOAD to a
function that reinvokes vmxon with the right address on each CPU during resume.
 Probably both bhyve and vbox should also fail to load in MOD_LOAD if that
pointer is already non-NULL which would enforce only one could be used at a

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-virtualization mailing list