Saw this same issue on the released 5.2.2, tried under test builds and still same problem.
Using 5.2.3-119658, with Sergio Basto's 4.15 patch applied to
timer-r0drv-linux.c
The resulting source tree builds cleanly and modprobes all 4 modules just fine.
Booting a Windows 7 or Windows 10 image crashes, usually about 10 seconds
in, but one lived 50 seconds.
Relevant part of the log:
00:00:10.164872 !!
00:00:10.164873 !! {vgasr}
00:00:10.164873 !!
00:00:10.164878 VGA Sequencer (3C5): SR index 3C4:04
00:00:10.164883 SR00:03 SR01:00 SR02:0F SR03:00 SR04:0A SR05:00 SR06:00 SR07:01
00:00:10.164928 !!
00:00:10.164929 !! {vgatext}
00:00:10.164929 !!
00:00:10.164934 Not in text mode!
00:00:10.164937
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:10.165000 emR3Debug: rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:36.319011 GUI: User request to power VM off on Guru Meditation.
Full log attached. I can do a kernel bisect to find what changed in linux-next
and/or
apply instrumentation/debugging patches, if needed.
Windows_10-2017-12-14-14-26-48.log.gz
Description: Windows_10-2017-12-14-14-26-48.log.gz
_______________________________________________ vbox-dev mailing list [email protected] https://www.virtualbox.org/mailman/listinfo/vbox-dev
