Opened 16 years ago
Closed 16 years ago
#3596 closed defect (invalid)
Guru Meditation 1103 (VINF_EM_DBG_HYPER_ASSERTION) (pgmPoolTracDerefGCPhysHint)
Reported by: | Oskar Berggren | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 2.1.4 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Linux |
Description
Using Vista 32bit guest on Ubuntu 8.10 (kernel 2.6.27, x86_64) host.
Virtualbox suddenly warned about Guru medition and asked for shutdown. Just a few seconds after the virtualbox machine window had disappeared the host OS froze completely (no screen redraws, mouse pointer frozen, no longer responds to ssh requests or even ping).
Inside the guest I was currently typing in the editor window of Visual Studio.
00:16:46.426 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 00:16:46.426 !! 00:16:46.426 !! Guru Meditation 1103 (VINF_EM_DBG_HYPER_ASSERTION) 00:16:46.426 !! 00:16:46.436 !!Assertion Failed!! 00:16:46.436 Expression: <NULL> 00:16:46.436 Location : /home/vbox/vbox-2.1.4/src/VBox/VMM/VMMAll/PGMAllPool.cpp(3243) void pgmPoolTracDerefGCPhysHint(PGMPOOL*, PGMPOOLPAGE*, RTHCPHYS, RTGCPHYS)
I actually have frequent guest and/or host crasches and I suspect virtualbox is causing them. This however is the first time I've seen the guru meditation dialog. Usually instead the whole virtualbox process dies and often the host OS crashes to.
Attachments (2)
Change History (5)
by , 16 years ago
by , 16 years ago
Attachment: | 20090319-kernel.log added |
---|
comment:1 by , 16 years ago
For the crash on 2009-03-26, which the VBox.log file is from I was unable to find any host kernel output in the log files.
20090319-kernel.log is the kernel output from another crash. It is possible that this is a completely different issue. In this instance there was no guru meditation. It just died.
comment:2 by , 16 years ago
Evidence seems to suggest that my stability problems, and possibly this Guru Med. was related to faulty memory. After discovering problems using memtest86+ I've since replaced the faulty module, and so far the system, including virtualbox, seems much more stable.
comment:3 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Thanks for the feedback. It is important that we are made aware of false alarms as soon as possible.
Example of kernel logs from another crash