Le 11/03/2018 à 22:30, Joerg Sonnenberger a écrit :
On Sat, Mar 10, 2018 at 06:58:39PM +0100, Maxime Villard wrote:
Le 09/03/2018 à 20:33, Joerg Sonnenberger a écrit :
On Fri, Mar 09, 2018 at 06:36:45PM +0100, Maxime Villard wrote:
Le 09/03/2018 à 18:14, Joerg Sonnenberger a écrit :
On Mon, Feb 26, 2018 at 05:52:50AM +0000, Maxime Villard wrote:
Module Name: src
Committed By: maxv
Date: Mon Feb 26 05:52:50 UTC 2018
Enable SVS by default.
This broke using VirtualBox and I wouldn't be surprised by other
virtualisation solutions to be affected as well.
I'm using VirtualBox with SVS enabled, and have been doing this for two
months already, everything works fine for me.
I get an instant guru meditation once the kernel is loaded and starting.
hardware-assisted or not? I use hardware-assisted, 4.x and 5.x.
Haswell, using VTx. It seems to hit a triple fault in db_panic according
to the vbox.log.
At which stage of the boot procedure does it happen? Does it happen right
before init is launched? Or does the kernel fault right after the bootloader?