Date: Wed, 29 Jun 2022 07:52:35 +0200 From: Tamas Szakaly <sghctoma@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: how to run bhyve and virtualbox at the same time Message-ID: <20220629055235.35suv34p5cbv2qtg@telaranrhiod> In-Reply-To: <1D2BDC88-6739-45E0-A609-98D6FF271733@aeichner.de> References: <CA%2B1FSig5qQRcQMm8uJ0A%2BNO1485MXsh_fEjMtU55iF_Qk0jn8w@mail.gmail.com> <62B9FBF1.6030906@grosbein.net> <CA%2B1FSihK9Q4cmthTyGb_TQLN_LOC%2B2GAiFoOOukQHGQ0Scuzsw@mail.gmail.com> <d76307e6-1e14-f58c-2d70-115b2d7cd5b2@FreeBSD.org> <1D2BDC88-6739-45E0-A609-98D6FF271733@aeichner.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, > On hosts other than Windows and macOS VirtualBox defaults to an exclusive use of VT-x/SVM for performance reasons. That mode can be changed > to do the initialization every time VirtualBox is scheduled on a particular CPU which has higher overhead but allows sharing the hardware virtualization capabilities > with other hypervisors. The setting can be changed with VBoxManage. Look at the manual under [1] and search for „hwvirtexclusive“. Sorry for the off-topic comment, but this might be interesting to other VirtualBox users: a happy side effect of turning "hwvirtexclusive" off is that it seems to solve the crash that occurs when the host is resuming from S3 sleep while having running VirtualBox VMs. Toma
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220629055235.35suv34p5cbv2qtg>