Ticket #14788 (closed defect: obsolete)
Windows Host Unresponsive when trying to start second VM with VMMR0.r0 ( VMMR0+1447c )
Reported by: | Peggy | Owned by: | |
---|---|---|---|
Component: | VMM | Version: | VirtualBox 5.0.8 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Windows |
Description (last modified by frank) (diff)
I have 2 Virtual servers I need to spin up at the same time. They are Oracle Linux images for Peoplesoft applications. Sometimes I can get both running and other times, I get the first one running and the other guest starts to boot but then the host becomes unresponsive and I have to power reset it. I have dump files from the last occurrence. Using Windows Debugger with the mini dump file seems to points to VMMR0.r0. I will post what log files I can but it seems like it does not actually write a log for the server that crashes the host (random as to which one).
******************************************************************************* * Bugcheck Analysis * ******************************************************************************* BugCheck 3B, {c000001d, fffff8009641747c, ffffd0019be86cd0, 0} *** WARNING: Unable to verify timestamp for VMMR0.r0 *** ERROR: Module load completed but symbols could not be loaded for VMMR0.r0 *** WARNING: Unable to verify timestamp for VBoxDrv.sys *** ERROR: Module load completed but symbols could not be loaded for VBoxDrv.sys Probably caused by : VMMR0.r0 ( VMMR0+1447c )
Attachments
Change History
Changed 5 years ago by Peggy
-
attachment
DisconnectHappensWhenStarting2ndVMAndHostBecomesUnresponsive.jpg
added
comment:1 Changed 5 years ago by Peggy
There was a second occurrence of this again yesterday. Two VMs were running, and a new third VM was created and started. It starts to boot but then the host becomes unresponsive and I had to power reset the host. I have the guest VM log file for that and am attaching it, along with the dump.
comment:3 Changed 12 months ago by aeichner
- Status changed from new to closed
- Resolution set to obsolete
Please reopen if this is still an issue with a recent VirtualBox release.