Guru Meditation Error Win11

[JonyGol]

Hi,

I have used Vbox only ca 2 months. I was using it for 1 month and there was no problem. then I didn't use it for a month, and when I tried to use it again now the Guru Meditation Error pops up.

To try and fix this I created a new VM, but it gives the same error as the first one did.

It is strange that it worked before, but now it is not working. I have a TcBSD machine running in the VM. The VM is installed with the guidance from this tutorial, and basically it is installed directly by a script. Nonetheless it has been working before, that is why I don't understand why it stopped to work all of a sudden.

[JonyGol]

sorry for the double post, I just wanted to add the zipfile of the log-files of the old machine.

I had to attach one file seperately to not exceed size limit

[multiOS]

Your VBoxLog(s) contain the following lines:

Code: Select all

00:00:02.615701 ********************* End of CFGM dump **********************
00:00:02.615759 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
00:00:02.665495 NEM:  info: Found optional import WinHvPlatform.dll!WHvQueryGpaRangeDirtyBitmap.
00:00:02.665569 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

which indicates MS Hyper-V is active.

MS Hyper-V and VirtualBox 6.1.34 don't play nicely together as Hyper-V currently prevents VirtualBox from accessing VT-x/AMD-V/ See: viewtopic.php?f=25&t=99390 for guidance on how to disable Hyoer-V.

The VirtualBox developers have been working on a solution for some time to this problem and the next VirtualBox (6.1.36) update may well provide a working solution fo those Windows users who really need both options.

[JonyGol]

I will follow those steps. However I am pretty sure that I have been struggling with turning off HyperV before already.

Isn't it strange though that it used to work, then I didn't use it since ca beginnig of May, and now when I try to launch it again it doens't work. Quite confusing for me.

[multiOS]

Isn't it strange though that it used to work, then I didn't use it since ca beginnig of May, and now when I try to launch it again it doens't work. Quite confusing for me.

Not at all strange IMO as, if you tracked Windows development, you would see that there have been constant changes over several years in the way MS has made increasing use of hardware virtualisation features which have not only been limited to OS virtualisation, but also in a much increased (and still increasing) use of VBS (Virtualisation Based Security) features. Many of these 'advances', which have continued further with the introduction of Windows 11 and its elevated hardware requirements, seem to have impacted negatively on third-party application developers whose products also rely on having equality of/shared access to hardware virtualisation. Some of those third-party products, e.g security applications (Ant-Virus/Malware) also seem to be making an increased use of hardware virtualisation availability to speed up live scanning, which can also impact negatively on OS Virtualisation Products if they don't share that access nicely with other trusted applications.

Meanwhile, if you want to test the upcoming release of VirtualBox you could install the latest Test Build (6.1.x revision 151573, or later) available here: https://www.virtualbox.org/wiki/Testbuilds, but to install Test builds on Windows you do need to temporarily disable UEFI Secure Boot, and you must also make sure you keep copies of the downloaded installers until the next official release is successfully installed, in case the Test Build needs to be uninstalled.

[JonyGol]

Meanwhile, if you want to test the upcoming release of VirtualBox you could install the latest Test Build (6.1.x revision 151573, or later) available here: **LINK**, but to install Test builds on Windows you do need to temporarily disable UEFI Secure Boot, and you must also make sure you keep copies of the downloaded installers until the next official release is successfully installed, in case the Test Build needs to be uninstalled.

Thank you, I will try that. You mean that I should save the installer file for the test build? I will do that?

[scottgus1]

keep copies of the downloaded installers

I should save the installer file for the test build?

Yes, these are the same concept.

[JonyGol]

I have tried installing the new testbuild version, but unfortunately I get the same error.

I also did a windows cummulative update, but that didn't change anything either.

I notice that I have done these updates during the time I didn't use VM. Maybe these are the ones causing the problems...

2022-05 Cumulative Update for ,NET Framework 3.5 and 4.8 for Windows 11 for x64 (KB5013628)

2022-05 Cumulative Update for Windows 11 for x64-based Systems (KB5013943)

[multiOS]

So, the mystery continues!

As there has been a number of software changes it would probably help to see the latest 'VirtualBox log' for the latest failed Windows 11 run which might provide more pointers to the ongoing problem. Just the one log as a zipped file should be sufficient, as the Hardening Log doesn't appear to indicate any problems with any 'adversaries'.

As your host is Windows Server it might also be useful to check whether any of the VBS (Virtualisation Based Security) settings have been activated. If they have, then there is likely to be a negative impact on VirtualBox performance. This 3rd-Party Guide might be useful for background: https://www.techspot.com/news/91613-her ... ws-11.html

I presume you have been using the widely published 'bypass hacks' to get Windows 11 to install on VirtualBox 6.1.34 (and Test Build 6.1.35) as these versions don't claim to be fully compatible with Windows 11 (Host or Guest).

[JonyGol]

As there has been a number of software changes it would probably help to see the latest 'VirtualBox log' for the latest failed Windows 11 run which might provide more pointers to the ongoing problem. Just the one log as a zipped file should be sufficient, as the Hardening Log doesn't appear to indicate any problems with any 'adversaries'.

I have provided here the latest logfile. I was thinking to only attach the "VBox" file, but I didn't know if that was the one you where looking for, so I attached them all except the hardening.

BE AWARE!
I actually have tried to de-install some of the Windows updates that I could see where installed during May, but ufortunately the problem persisted. I now have a pending update that I will install after this.
I also have uninstalled VM Virtualbox and re-installed it, installed the testbuild (v1.35...) and then re-installed the previous version "Version 6.1.34 r150636 (Qt5.6.2)". The problem was there for all different combinations..

As your host is Windows Server it might also be useful to check whether any of the VBS (Virtualisation Based Security) settings have been activated. If they have, then there is likely to be a negative impact on VirtualBox performance. This 3rd-Party Guide might be useful for background: https://www.techspot.com/news/91613-her ... ws-11.html

I will check on this. I believe that I have looked at it before and done the necessary steps, but doesn't hurt to control again.

I presume you have been using the widely published 'bypass hacks' to get Windows 11 to install on VirtualBox 6.1.34 (and Test Build 6.1.35) as these versions don't claim to be fully compatible with Windows 11 (Host or Guest).

Yes, I did it through windows powershell

[fth0]

All your VBox.log files show more or less the same: VirtualBox 6.1.34 using NEM mode because Hyper-V is running on your host. This combination is well known to have issues.

If you provided a VBox.log file from a run with VirtualBox 6.1.35r151573 (or newer), we could assess if it would make sense to create a ticket in the Bugtracker.

If you'd succeed in disabling Hyper-V on the host and provided a VBox.log file of VirtualBox 6.1.34 not using NEM mode, we could assess if it would make sense to create a ticket in the Bugtracker.

Alternatively, you could try to provide 2 vCPUs to the VM, which has helped some VirtualBox users in similar situations.

[JonyGol]

If you provided a VBox.log file from a run with VirtualBox 6.1.35r151573 (or newer), we could assess if it would make sense to create a ticket in the Bugtracker.

Here is the log-file. I provided only the VBox.log file (not the Vbox.log.1) because I saw that this file was the only file that was edited today, when I ran the new version.

If you'd succeed in disabling Hyper-V on the host and provided a VBox.log file of VirtualBox 6.1.34 not using NEM mode, we could assess if it would make sense to create a ticket in the Bugtracker.

Next step is to double check this, but I'm not really managing to turn it off..

[fth0]

Ok, the Guru Meditation in VirtualBox 6.1.34 and 6.1.35r151573 is really the same. Please create a ticket in the Bugtracker. I'd suggest to make the following part of the title: "Guru Meditation -6893 (VERR_NEM_IPE_3)".

Additionally, please try if providing 2 vCPUs to the VM or disabling large pages (VBoxManager modifyvm "TcBSD_x64" --largepages off) helps.

[JonyGol]

Additionally, please try if providing 2 vCPUs to the VM or disabling large pages (VBoxManager modifyvm "TcBSD_x64" --largepages off) helps.

Wow, this actually worked! I added so that the VM had 2 CPU's available. Then the VM started! ========)

NOTE:
I have installed a Beckhoff TcBSD, so my machine is actually a kind of virtual PLC. No it starts as it should.

Thank you all for the help!!