Custom Query (16363 matches)
Results (1255 - 1257 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #18048 | fixed | "SUPLIB not initiated successfully" with --disable-hardening --build-debug ==> fixed in SVN | ||
| Description |
In VirtualBox-5.2.18/src/VBox/VMM/VMMR3/VM.cpp
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 |
|||
| #18046 | fixed | another VMMR0.r0 BSOD => fixed in svn | ||
| Description |
I noticed it few months (year?) ago, and it's still not fixed. Regardless of Win host system all guests fails sometimes with bridged networking on Realtek 8111F, with BSOD. NAT works correctly. I also have the latest drivers for every aspect in my system (so in this case it is 10.30.815.2018, but it happened with different version of W10, and drivers). Other systems with Intel cards (e.g. I219-V) are not affected. Every time when the guest is performing some network activity the host is crashed with STOP "driver irql not less or equal" error. (log and dump attached). |
|||
| #18044 | duplicate | Virtual box starts up in the background | ||
| Description |
I have tree different locations/workplaces with different monitor setup using dockingstations. on two of the locations virtualbox won't start so it is visible. I can see it virtualbox is active in the background and first thought is that it didn't double click and endend up starting it several times in the background. However i found out can disconnect the dockingstation and virtualbox startup/is visible on my screen. Now i can connect the dockingstation again and work with virtualbox. Anyway to avoid this behavior? |
|||

