virtualbox.org

HP EliteBook 8470p
Window 7 64-bit 8GB Mem, Intel I5 Quad Core
Guest OS: Solaris 10 update 11
VirtualBox: 4.3.12 r93733
Error MSG: A critical error has occurred while running the virtual machine and the machine execution has been stopped.

This appears to happen when the host OS, Windows 7 turns off the display. I may be wrong about this, but I seem to have the issue when I return to my computer after the screen has been blanked, not all the time though. This is a company PC so it's locked down by IT and I don't have complete control over it. I would like to disable the screen blanking and turn on hardware virtualization in the Bios, but I can't at the moment...

This problem occurs about 2 - 3 times a week.

I've attached the log and image file when the issue occurred.

I appreciate any and all suggestions

Thank You in Advance
Dennis

You have the following in your log:

02:13:48.488854 !! Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

For Guru Meditation errors, you should head to the bugtracker and either search for an appropriate bug where you'll attach your logs and other vital information, or open a new bug report.

The funny thing is that you get it after 2-hours of operation. Usually most of the ones that I've seen are in the first few seconds. But, as I said, only the developers can make heads or tails out of this.

The other thing that I noticed is that the logs of your VM lists the guest as 'OpenSolaris', not as 'Solaris11_64' or something of that nature. Could this be the culprit?

socratis ,

thanks I did just that... Posted it against TKT 12926 which is also a Windows 7 host with a similar problem...

It happened again but no guru meditation errors... Ran for almost 2 weeks without an issue. the first 2 entries, 00:00:16.960816 , 870 were the last 2 entries in the log when I resumed my guest session. Then there is the geometry changed msg and a black screen and then it eventually reboots.

I saw the black screen and while I was looking at this log the guest rebooted I did not initiate it..

This is what has me scratching my head, the following lines, I didn't initiate the reset...

02:22:40.847897 Reset initiated by keyboard controller
02:22:40.847955 Changing the VM state from 'RUNNING' to 'RESETTING'.

00:00:16.960816 NAT: DNS#0: 192.168.10.241
00:00:16.960870 NAT: DHCP offered IP address 10.0.2.15
01:44:02.766583 UIMachineLogic: Host-screen geometry changed.
01:44:03.771722 VMMDev::SetVideoModeHint: got a video mode hint (1600x836x0)@(0x0),(1;0) at 0
01:44:04.064887 Guest Additions capability report: (0x5 -> 0x5) seamless: yes, hostWindowMapping: no, graphics: yes
01:44:04.065052 VBVA_INFO_SCREEN: [0] @0,0 1600x806, line 0x1900, BPP 32, flags 0x1
01:44:04.116651 Guest Additions capability report: (0x5 -> 0x5) seamless: yes, hostWindowMapping: no, graphics: yes
01:44:04.116783 VBVA_INFO_SCREEN: [0] @0,0 1600x836, line 0x1900, BPP 32, flags 0x1
01:44:04.116855 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000009e10000 w=1600 h=836 bpp=32 cbLine=0x1900, flags=0x1
01:44:04.131854 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000009e10000 w=1600 h=836 bpp=32 cbLine=0x1900, flags=0x1
02:21:55.063917 UIMachineLogic: Host-screen geometry changed.
02:21:55.252273 VMMDev::SetVideoModeHint: got a video mode hint (1600x806x0)@(0x0),(1;0) at 0
02:21:55.481941 Guest Additions capability report: (0x5 -> 0x5) seamless: yes, hostWindowMapping: no, graphics: yes
02:21:55.482080 VBVA_INFO_SCREEN: [0] @0,0 1600x836, line 0x1900, BPP 32, flags 0x3
02:21:55.482161 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=1600 h=836 bpp=0 cbLine=0x0, flags=0x3
02:21:55.547888 Guest Additions capability report: (0x5 -> 0x5) seamless: yes, hostWindowMapping: no, graphics: yes
02:21:55.548062 VBVA_INFO_SCREEN: [0] @0,0 1600x836, line 0x1900, BPP 32, flags 0x3
02:21:55.548154 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=1600 h=836 bpp=0 cbLine=0x0, flags=0x3
02:21:58.714759 AHCI#0: Port 0 reset
02:22:40.847897 Reset initiated by keyboard controller
02:22:40.847955 Changing the VM state from 'RUNNING' to 'RESETTING'.
02:22:40.888590 CPUM: SetGuestCpuIdFeature: Enabled APIC
02:22:40.888647 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
02:22:40.902613 AHCI#0: Reset the HBA
02:22:41.350255 UIMachineLogic: Guest-screen count changed.
02:22:41.498934 Changing the VM state from 'RESETTING' to 'RUNNING'.
02:22:41.499007 OHCI: root hub reset completed with VINF_SUCCESS
02:22:41.517318 Guest Log: BIOS: VirtualBox 4.3.12

Any and all help appreciated
Thanks
Dennis

I notice that according to the log you have a very low VRAM setting - 12MB, despite using a largish display size - 1600x836x32bpp. Isn't there red text on the settings dialog warning you about this? Your host has plenty of RAM so I would up this until the warning disappears. Around 32MB should be good. Shut down (not suspend) your VM to make the change.

Thanks for the suggestion, I increased it to 32mb, I know if I go below the 12mb it will turn red...

I'll run it and see what happens. I'll geve it a few weeks to see if that is the issue.

Thanks Again
Dennis

It's been 7 days since the last incident. What I find puzzeling is the following line in the logs:
05:18:15.845825 Reset initiated by keyboard controller

This Time I was away from my notebook and when I returned I found that VitualBox had restarted my Guest OS. It looks like the signature is UIMachine:Logic : Host-screen geometry changed and then the 'Reset initiated by keyboard controller'...

I've attached the full log.


00:00:19.080798 NAT: DHCP offered IP address 10.0.2.15 <<< Running for 5 hours and 17 minutes
05:17:29.204725 UIMachineLogic: Host-screen geometry changed.
05:17:29.487358 VMMDev::SetVideoModeHint: got a video mode hint (1600x836x0)@(0x0),(1;0) at 0
05:17:29.738720 Guest Additions capability report: (0x5 -> 0x5) seamless: yes, hostWindowMapping: no, graphics: yes
05:17:29.738901 VBVA_INFO_SCREEN: [0] @0,0 1600x806, line 0x1900, BPP 32, flags 0x1
05:17:32.087051 AHCI#0: Port 0 reset
05:18:15.845825 Reset initiated by keyboard controller
05:18:15.845881 Changing the VM state from 'RUNNING' to 'RESETTING'.
05:18:15.863959 CPUM: SetGuestCpuIdFeature: Enabled APIC
05:18:15.864013 PIT: mode=3 count=0x10000 (65536) - 18.20 Hz (ch=0)
05:18:15.866843 AHCI#0: Reset the HBA
05:18:16.183011 Changing the VM state from 'RESETTING' to 'RUNNING'.
05:18:16.183081 OHCI: root hub reset completed with VINF_SUCCESS
05:18:16.185170 Guest Log: BIOS: VirtualBox 4.3.12
05:18:16.185402 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
05:18:16.210148 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
05:18:16.229851 AHCI#0: Reset the HBA
05:18:16.230826 AHCI#0: Port 0 reset
05:18:16.231818 Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 33554432 sectors
05:18:16.232041 AHCI#0: Port 1 reset
05:18:16.232306 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
05:18:16.256210 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=000000000a7d0000 w=640 h=480 bpp=32 cbLine=0xA00, flags=0x1
05:18:18.470466 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0, flags=0x1
05:18:18.474580 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
05:18:18.475259 Guest Log: BIOS: Boot : bseqnr=1, bootseq=0023
05:18:18.477072 Guest Log: BIOS: CDROM boot failure code : 0003
05:18:18.477262 Guest Log: BIOS: Boot from CD-ROM failed
05:18:18.477434 Guest Log: BIOS: Boot : bseqnr=2, bootseq=0002
05:18:18.502658 Guest Log: BIOS: Booting from Hard Disk...
05:18:18.521457 Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=81

Reset initiated by keyboard controller means that the guest has requested the reboot. I would search bugtracker for an open ticket or create one yourself. I found this one but there may be others. https://www.virtualbox.org/ticket/11398

Since my last post I have enable HW virtualization in the BIOS and have loaded a 64 bit version of Solaris, Solaris 11.2. To date this issue has not happened again.

I think increasing the Video memory made a difference, bumped it up to 32MB but the fix IMO was enabling the HW virtualization in the BIOS and installing a 64 bit OS.

Dennis