Critical Error (Guru) 5.2.12

[LJMM]

Hello

I have been using Virtual Box for years and suddenly received a "critical error" message with a guru character inviting me to debug (requires specialist skills & tools, apparently) or to turn to this forum for assistance.

I was wondering if anyone could help me find a solution to this as I am completely at a loss. I have just updated to 5.2.12 from a much earlier version and also installed the extension package.

The very end of the VBox.log has this:

Code: Select all

00:14:22.783578 ********************* End of statistics **********************
00:14:22.805357 NAT: Zone(nm:mbuf_cluster, used:0)
00:14:22.806078 NAT: Zone(nm:mbuf_packet, used:0)
00:14:22.806091 NAT: Zone(nm:mbuf, used:1)
00:14:22.806114 NAT: Zone(nm:mbuf_jumbo_pagesize, used:0)
00:14:22.806484 NAT: Zone(nm:mbuf_jumbo_9k, used:0)
00:14:22.806728 NAT: Zone(nm:mbuf_jumbo_16k, used:0)
00:14:22.806776 NAT: Zone(nm:mbuf_ext_refcnt, used:0)
00:14:22.807050 E1000#0 Interrupt attempts: 409
00:14:22.807058 E1000#0 Interrupts raised : 207
00:14:22.807061 E1000#0 Interrupts lowered: 0
00:14:22.807065 E1000#0 ICR outside ISR   : 14
00:14:22.807068 E1000#0 IMS raised ints   : 0
00:14:22.807071 E1000#0 Interrupts skipped: 173
00:14:22.807075 E1000#0 Masked interrupts : 29
00:14:22.807078 E1000#0 Early interrupts  : 0
00:14:22.807081 E1000#0 Late interrupts   : 0
00:14:22.807084 E1000#0 Lost interrupts   : 0
00:14:22.807087 E1000#0 Interrupts by RX  : 35
00:14:22.807090 E1000#0 Interrupts by TX  : 184
00:14:22.807093 E1000#0 Interrupts by ICS : 4
00:14:22.807096 E1000#0 Interrupts by RDTR: 0
00:14:22.807099 E1000#0 Interrupts by RDMT: 0
00:14:22.807102 E1000#0 Interrupts by TXQE: 0
00:14:22.807105 E1000#0 TX int delay asked: 0
00:14:22.807108 E1000#0 TX delayed:         0
00:14:22.807111 E1000#0 TX delay expired:   0
00:14:22.807114 E1000#0 TX no report asked: 49
00:14:22.807117 E1000#0 TX abs timer expd : 0
00:14:22.807120 E1000#0 TX int timer expd : 0
00:14:22.807123 E1000#0 RX abs timer expd : 0
00:14:22.807126 E1000#0 RX int timer expd : 0
00:14:22.807129 E1000#0 TX CTX descriptors: 49
00:14:22.807132 E1000#0 TX DAT descriptors: 154
00:14:22.807135 E1000#0 TX LEG descriptors: 66
00:14:22.807138 E1000#0 Received frames   : 35
00:14:22.807141 E1000#0 Transmitted frames: 184
00:14:22.807144 E1000#0 TX frames up to 1514: 184
00:14:22.807147 E1000#0 TX frames up to 2962: 0
00:14:22.807150 E1000#0 TX frames up to 4410: 0
00:14:22.807153 E1000#0 TX frames up to 5858: 0
00:14:22.807156 E1000#0 TX frames up to 7306: 0
00:14:22.807159 E1000#0 TX frames up to 8754: 0
00:14:22.807162 E1000#0 TX frames up to 16384: 0
00:14:22.807165 E1000#0 TX frames up to 32768: 0
00:14:22.807168 E1000#0 Larger TX frames    : 0
00:14:22.807171 E1000#0 Max TX Delay        : 0
00:14:22.810351 Changing the VM state from 'DESTROYING' to 'TERMINATED'
00:14:22.816636 Console: Machine state changed to 'PoweredOff'
00:14:23.527960 GUI: Passing request to close Runtime UI from machine-logic to UI session.

I would be so grateful for any insights/help. Thank you in advance!

[socratis]

The very end of the VBox.log...

Partial logs are not that helpful I'm afraid. Please ZIP and attach the full log. See the "Upload attachment" tab below the reply form.

[LJMM]

Hello Socratis

Thanks so much for getting in touch (and for asking me to do the obvious...)

Unfortunately, this problem plunged me into deadline hell and I am only now able to turn my attention back to it.

I have now attached the full .log file - is there any chance you could have a look and let me know if it shows the root of the problem?

Thanks very much in advance.

BW

Liisa

[socratis]

There are several things that are different from your typical setup for a Win7 VM:

00:00:01.345053 File system of '/Users/amartin/VirtualBox VMs/Windows 7/Windows 7-disk1.vmdk' is hfs

How exactly did you get that VM? Where from? The naming and the file type are not the defaults for a VirtualBox VM.

00:00:01.376103 IOAPIC <integer> = 0x0000000000000000 (0)

That's typically enabled for a Win7 VM, but that's relatively OK.

00:00:01.376113 ShowCpu <integer> = 0x0000000000000000 (0)

If anyone knows what this is, please post a comment. I took a look at my logs, and I have it on VMs like DOS, WfW, WinNT<4, OS/2, etc. I don't know what it is, what it does, but I don't think it should be off. The thing is I don't know how did that thing got in there. Maybe a consequence of the I/O APIC?

Edit: Yes, it is due to the I/O APIC being disabled. Still don't know what it means...

@LJMM, right-click on the VM, "Show in Finder". ZIP that .vbox file and attach it here.

00:00:01.376220 [/Devices/ichac97/0/] (level 3)

Why do you have the ICH97 selected as your sound card? There are no default drivers for a Win7 setup, you'd need to download something external.

00:00:01.376355 Path <string> = "/Applications/VirtualBox.app/Contents/MacOS/VBoxGuestAdditions.iso" (cb=67)

Eject your Guest Additions (GAs) CD when you're done with the installation. If you upgrade your VirtualBox with your CD not ejected, you're going to have issues.

00:00:01.646827 Host path '/Volumes/OLIVIA USB', map name 'OLIVIA_USB', writable, automount=true,
                create_symlinks=false, missing=true
00:00:01.647242 Host path '/Users/amartin/Desktop/WIN-MAC', map name 'WIN-MAC', writable, automount=true,
                create_symlinks=false, missing=true

When your VM starts with warnings, please do not ignore them. Remove the shared folders that don't exist.

00:00:18.188880 VMMDev: Guest Additions information report: Version 4.1.2 r73507 '4.1.2'

Those are some quite old additions you have there. You'll need to update them!