VirtualBox

Ticket #18048 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

"SUPLIB not initiated successfully" with --disable-hardening --build-debug ==> fixed in SVN

Reported by: Cake Owned by:
Component: VMM Version: VirtualBox 5.2.18
Keywords: Cc:
Guest type: Windows Host type: Linux

Description

In VirtualBox-5.2.18/src/VBox/VMM/VMMR3/VM.cpp

  • Line 212 calls VMR3GlobalInit, which eventually ends up calling suplibOsIOCtl.
  • Line 238 calls SUPR3Init, which is too late.

The VM starts when I call SUPR3Init(NULL) earlier. I attached a patch, but I assume you will know how to fix it better.

I see someone else has experienced this issue before:  https://forums.virtualbox.org/viewtopic.php?f=10&t=84300

Attachments

VBox.log.1 Download (1.3 KB) - added by Cake 3 years ago.
sup-backtrace.txt Download (2.4 KB) - added by Cake 3 years ago.
initialize-sup.patch Download (443 bytes) - added by Cake 3 years ago.

Change History

Changed 3 years ago by Cake

Changed 3 years ago by Cake

Changed 3 years ago by Cake

comment:1 Changed 3 years ago by bird

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from "SUPLIB not initiated successfully" with --disable-hardening --build-debug to "SUPLIB not initiated successfully" with --disable-hardening --build-debug ==> fixed in SVN

This shouldn't normally happen if vboxdrv is working an accessible and the application called RTR3InitExe w/ RTR3INIT_FLAGS_SUPLIB, however I see it could be annoying, so I've moved the probe initialization down till after the SUPR3Init call. The changes will make it out to SVN before long, I hope.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use