VirtualBox

Ticket #8104 (new defect)

Opened 3 years ago

Last modified 3 years ago

VERR_VMM_RING0_ASSERTION guru meditation (win32 debug build)

Reported by: mhanor Owned by:
Priority: minor Component: other
Version: VirtualBox 4.0.0 Keywords:
Cc: Guest type: Windows
Host type: Windows

Description

SVN 35582, win32 debug build using VS2010, WDK 7600.1, Qt 4.7.1, host XP SP3 32 bit. I can't reproduce it with the release build.

I've decided to open a bug because I can reproduce it every time, by trying to install XP SP3 32 bit as guest. At least, if it's a fresh install (it managed once to get past the issue after resuming the setup, but most of the times it doesn't, even if I try resuming the setup process). It always triggers it at some stage of "Installing Devices", during guest OS setup (the setup progress bar can be different). Also, I've encountered several "guru meditation" VM states, in the past, while installing the same guest on the same host, using the official win32 VirtualBox release, but each time I chose to ignore it and retry installing the OS, because it's so damn rare and it can't be reproduced at will.

Attachments

VBox.log Download (270.7 KB) - added by mhanor 3 years ago.
VBox.png Download (133.2 KB) - added by mhanor 3 years ago.

Change History

Changed 3 years ago by mhanor

Changed 3 years ago by mhanor

comment:1 Changed 3 years ago by mhanor

I forgot to mention, I even tried with no audio, no USB, no NX, no network adapter (VM settings).

comment:2 Changed 3 years ago by frank

Please don't report debug assertions here. These assertions are disabled in release builds. Some assertions are just false positives. The debug build is only for developers who know what they are doing, not for doing real work with. I would be rather interested in a VBox.log file of such a Guru meditation you get with a release build.

comment:3 Changed 3 years ago by mhanor

Sorry. I did ask, some time ago, on the IRC vbox dev channel, if I should report what I've already reported at #7165. I thought that, most of the times, failed asserts reveal real problems. I won't do it again, unless I understand what's going on. You can close this ticket, I'm pretty sure the guru meditation that I've encountered with the release build wasn't a VERR_VMM_RING0_ASSERTION assertion.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use