Date: Wed, 08 Aug 2018 18:10:32 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 229824] Fatal trap 1 when resuming from S3 with a VirtualBox VM running Message-ID: <bug-229824-27103-R0pkOxzzgr@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229824-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-229824-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229824 John Baldwin <jhb@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhb@FreeBSD.org --- Comment #1 from John Baldwin <jhb@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=3Drevision&revision=3D259782. We woul= d need something similar. The same issue matters for permitting multiple hypervis= ors 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/vm= xoff during context switch. Having that would also allow us to more cleanly han= dle 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 res= ume. 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 time. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229824-27103-R0pkOxzzgr>