VirtualBox

Ticket #12886 (closed defect: duplicate)

Opened 4 years ago

Last modified 3 years ago

Guru Meditation error -2403 with LSI Logic

Reported by: hwertz Owned by:
Priority: minor Component: other
Version: VirtualBox 4.3.10 Keywords:
Cc: Guest type: other
Host type: other

Description

I have been having Guru meditation errors in probably 1 out of 2 VM bootups (and if it does boot it may bail out later) with 4.3.x versions of VirtualBox. This includes 4.3.10. 4.2.24 (and 4.2.x in general) has worked fine. This is the case with Windows 7, Windows XP, and Ubuntu guests of several different versions. I'm running a Core Duo T2300 @ 1.66ghz (not Core 2 -- no VT-X!) with Ubuntu 12.04.4.

I had been just changing back to 4.2, but this time I decdied to look a little closer -- I noticed when it crashes during VM boot, it appears to be immediately after a scan of the SCSI bus, and speculated this may be related. I just tried moving my disk image from SCSI to SATA, and no more crashes! I left the component at "other" because I don't know if it'd be considered a virtual disk issue (since it involves a disk image attached to LSI) or VMM (since the crash itself is in VMMGC.gc).

I also noticed the CPUM in the log mis-identifes my CPU as a "Intel Xeon X5482 3.20GHz" but since it also appears to check CPU flags individually I don't think this affects anything.

VBox.log is Windows XP crashing, VBox.log.2 is it crashing again (I thought when I recorded them I got one from WinXP and one from Win7...), and VBox.log-working is a successful boot (a Windows 7 VM however.)

Attachments

VBox.log Download (252.8 KB) - added by hwertz 4 years ago.
First crash of Windows XP SP3
VBox.log-2 Download (260.6 KB) - added by hwertz 4 years ago.
Second crash of Windows XP SP3
VBox.log-working Download (88.7 KB) - added by hwertz 4 years ago.
Here's Windows 7 successfully booting
VBox-4.3.12.headless.upgrade.GuruMeditation2403.20140522-1.log Download (219.6 KB) - added by cal 4 years ago.
Upgrade attempt from 4.2.22 to 4.3.12 - boot headless
VBox-4.3.12.console.upgrade.GuruMeditation2403.20140522-2.log Download (442.1 KB) - added by cal 4 years ago.
Upgrade attempt from 4.2.22 to 4.3.12 - boot from VBox console
VBox-4.2.22.headless.downgrade.NoErrors.20140522.log Download (47.0 KB) - added by cal 4 years ago.
Normal headless boot with 4.2.22

Change History

Changed 4 years ago by hwertz

First crash of Windows XP SP3

Changed 4 years ago by hwertz

Second crash of Windows XP SP3

Changed 4 years ago by hwertz

Here's Windows 7 successfully booting

comment:1 Changed 4 years ago by hwertz

Ugh.. can someone please change "host type" to Linux and "guest type"... well, the logs I have here are for Windows but it did it for both Windows and Linux as I said. I missed those dropdowns when I started going to attach the logs, and realized I can't change them now. Thanks!

comment:2 Changed 4 years ago by cal

I'm seeing the same thing. We've been running VirtualBox 4.2.22 for quite some time because the 4.3 versions have not been working for us.

CPU: (dual) Intel 80546K Xeon Nocona (no VT extensions) CentOS 6.5 fully updated VirtualBox 4.2.22 with guest additions VBox Guest: (headless) Windows Server 2003 using vdi disk on Lsilogic SCSI controller

Just tried installing the 4.3.12 update with guest additions and got "Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)" on boot. First, I removed the 4.2.22 installation. Then installed fresh the 4.3.12 version followed by guest additions. Everything looked normal until the Windows logo appeared. Immediately went into "Guru Meditation"

Attaching log "VBox-4.3.12.headless.upgrade.GuruMeditation2403.20140522-1.log" from this first attempt.

Killed all the VirtualBox processes and restarted the guest from the management console. This time it booted up all the way but went into Guru Meditation with same error shortly after logging in.

Attaching log "VBox-4.3.12.console.upgrade.GuruMeditation2403.20140522-2.log" from the second attempt.

I tried switching to the SATA controller as mentioned above but that failed with repeated Blue Screen errors. Also tried the BusLogic SCSI controller with similar results.

Removed VBox 4.3.12 and re-installed the old 4.2.22. Although it is slow and something of a memory hog, it does work.

Attaching log "VBox-4.2.22.headless.downgrade.NoErrors.20140522.log" from normal headless boot with version 4.2.22.

Changed 4 years ago by cal

Upgrade attempt from 4.2.22 to 4.3.12 - boot headless

Changed 4 years ago by cal

Upgrade attempt from 4.2.22 to 4.3.12 - boot from VBox console

Changed 4 years ago by cal

Normal headless boot with 4.2.22

comment:3 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to duplicate

Finally found and fixed. The fix will be part of the next maintenance release. This is the same problem as #12774.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use