Opened 9 years ago
Closed 4 years ago
See attached log file
Download all attachments as:
have also tried 4.3.27 test build
Thanks for the log files. We saw very rare reports like this in the past (VERR_VMX_INVALID_VMXON_PTR Gurus) but were never able to reproduce this. Do you have any software running on the host worth to mention which could interfere with VirtualBox, like another virtualization application?
Not knowingly. My host is a corporate build of 64bit Windows 7. In task manager I can see some Microsoft Virtualisation stuff: I have attached screenshot.
I tried stopping all those processes, but still got the crash.
One further question: Did you use any version of VirtualBox before where this didn't happen, i.e. is this problem a (recent?) regression?
This sounds like an issue I was having.
When we were getting Guru meditation, within a second of a Meditation, Windows Event Viewer was making comments about adjusting VM settings, and starting new VMs. Which is interesting as these messages were attached to ‘Windows Virtual PC’.
I think I had had a windows update which reactivated my old Windows Virtual PC.
To disable Windows Virtual PC on Windows 7
Control Panel > Programs and Features > Turn Windows features on or off > untick Windows Virtual PC (third from the bottom)
Me and 5+ people were getting this issue in our office, and since we have disabled Windows Virtual PC, we stopped getting guru meditations :D
Hope this is useful, if not good luck.
The next maintenance version of VirtualBox should contain some extra bits of diagnostic information when the guru happens. At the moment, we cannot see anything wrong with our code and I strongly suspect this is due to some other programs on the host OS that interferes with our VT-x usage.
Log from 4.3.28 crash
Another crash of 4.3.28 with possibly more info.
Can confirm that disabling the Windows Virtual PC fixes the issue.
I had been experiencing the same problem with my virtual machines going into guru mediation. I therefore followed the instruction to uninstall the Windows Virtual PC software as stated by the user Clemi and the issue has now stopped. Hence, I can confirm that uninstalling the Windows Virtual PC software resolved the issue for me.
Powered by Trac 18.104.22.168
By Edgewall Software
© 2023 Oracle