Host: Windows Server 2003 64bit SP2
VirtualBox: v5.0.0 r101573
VM: Other Linux, 2GB RAM
My VM changed state to "Guru Meditation", below you find a section of the log:
331:24:19.400812 !!
331:24:19.400813 !! {vgagr}
331:24:19.400814 !!
331:24:19.400815 VGA Graphics Controller (3CF): GR index 3CE:05
331:24:19.400816 GR00:00 GR01:00 GR02:00 GR03:00 GR04:00 GR05:50 GR06:05 GR07:0F GR08:FF
331:24:19.400822 !!
331:24:19.400823 !! {vgapl}
331:24:19.400824 !!
331:24:19.400825 read mode : 0 write mode: 0
331:24:19.400826 set/reset data: 00 S/R enable: 00
331:24:19.400828 color compare : 00 read map : 0
331:24:19.400829 rotate : 0 function : 0
331:24:19.400831 don't care : 0F bit mask : FF
331:24:19.400832 seq plane mask: 0F chain-4 : on
331:24:19.400834 !!
331:24:19.400835 !! {vgasr}
331:24:19.400836 !!
331:24:19.400837 VGA Sequencer (3C5): SR index 3C4:04
331:24:19.400838 SR00:03 SR01:00 SR02:0F SR03:00 SR04:0A
331:24:19.400842 !!
331:24:19.400843 !! {vgatext}
331:24:19.400844 !!
331:24:19.400845 Not in text mode!
331:24:19.400847 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
331:24:19.407991 emR3Debug: rc=VINF_EM_TRIPLE_FAULT
331:24:20.416790 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
331:24:20.460226 Console: Machine state changed to 'GuruMeditation'
What should I do to avoid this problem?
Guru Meditation Problem!
-
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Guru Meditation Problem!
Post the guests log file ( as an attachment ) showing the mediation.
Re: Guru Meditation Problem!
PFA the log files
- Attachments
-
- VBoxStartup.log
- (110.8 KiB) Downloaded 16 times
-
- VBox.log
- (123.03 KiB) Downloaded 19 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Guru Meditation Problem!
Those log files do not look correct. VBoxStartup is not required, since you don't have a problem starting the VM (only the guest OS). It would help if you compressed such large files before attaching them (e.g. zip them).
In the VBox.log file, one huge problem is immediately apparant :-
In the VBox.log file, one huge problem is immediately apparant :-
This is not enough available memory for most VMs.VBox.log wrote: 00:00:02.154197 Host RAM: 5117MB total, 199MB available