Hi, I tried to start up a VM but this error comes up inmediatly. My SO is windows 7 and my VM is windows 10.
This VM has been tested on other PCs working well.
Please check the attached files. I hope you can help me. Thanks in advance.
Critical error has occurred while running virtualbox
Critical error has occurred while running virtualbox
- Attachments
-
- Logs.zip
- (254.51 KiB) Downloaded 15 times
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Critical error has occurred while running virtualbox
You had a Guru Meditation.
The IEM thing is a new problem that has arisen. Try reverting to 6.0.14 with matching extension pack, see if the guest can start. If so, zip and post a log from that successful run for comparison.00:00:02.006197 VirtualBox VM 6.1.0 r135406 win.amd64 (Dec 10 2019 14:34:16) release log 00:00:06.251267 IEM: wrmsr(0xc0000080,0x0`00000d00) -> #GP(0) 00:00:06.251674 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
-
- Volunteer
- Posts: 5668
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: Critical error has occurred while running virtualbox
You have to enable NX/XD in your host's BIOS settings to be able to execute a 64-bit guest OS in a VM.VBox.log file wrote:00:00:03.302676 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!
NX/XD + IA32_EFER MSR + Guru Meditation
If the NX/XD (No-Execute/Execute-Disable) CPU feature (Data Execution Prevention) is disabled in the host's (UEFI) BIOS, and the guest OS tries to set the NXE (NX enable) bit (11, 0x800) in the IA32_EFER MSR (Extended Feature Enable Register, 0xc0000080) to activate the unavailable NX/XD feature, it causes a Guru Meditation. The following lines in the VBox.log file indicate this behavior:
VBox.log file wrote:00:00:03.302547 HM: Host EFER = 0x501 [...] 00:00:03.302676 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it! [...] 00:00:03.303314 NX - No-Execute/Execute-Disable = 0 (0) [...] 00:00:06.251267 IEM: wrmsr(0xc0000080,0x0`00000d00) -> #GP(0) 00:00:06.251674 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
Re: Critical error has occurred while running virtualbox
Thanks for your help! This was really helpful!!
I just enable that option in host BIOS and it worked. I tried this solution firts because it was faster then going back to previous version of VB.
Thank you both.
I just enable that option in host BIOS and it worked. I tried this solution firts because it was faster then going back to previous version of VB.
Thank you both.
fth0 wrote:You have to enable NX/XD in your host's BIOS settings to be able to execute a 64-bit guest OS in a VM.VBox.log file wrote:00:00:03.302676 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it!
NX/XD + IA32_EFER MSR + Guru Meditation
If the NX/XD (No-Execute/Execute-Disable) CPU feature (Data Execution Prevention) is disabled in the host's (UEFI) BIOS, and the guest OS tries to set the NXE (NX enable) bit (11, 0x800) in the IA32_EFER MSR (Extended Feature Enable Register, 0xc0000080) to activate the unavailable NX/XD feature, it causes a Guru Meditation. The following lines in the VBox.log file indicate this behavior:
VBox.log file wrote:00:00:03.302547 HM: Host EFER = 0x501 [...] 00:00:03.302676 CPUM: WARNING! Can't turn on NX/XD when the host doesn't support it! [...] 00:00:03.303314 NX - No-Execute/Execute-Disable = 0 (0) [...] 00:00:06.251267 IEM: wrmsr(0xc0000080,0x0`00000d00) -> #GP(0) 00:00:06.251674 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'