Page 1 of 1
FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 12. Nov 2022, 03:09
by Jim Comfort
I recently upgraded VBox to 7.02, and while all my Windows and Linux VM's are working OK still, I'm getting a Guru Meditation error on starting up any of my BSD VM's. The error is VERR_VMX_INVALID_GUEST_STATE. I can't find much on that particular error when Googling it. Strangely enough, I hit the "one" key a few times during my last attempt, and apparently the VM kicked in before the error, because it booted, and seemed to run fine in the session. After exiting the VM through the OS, I tried restarting the VM, and without tapping any keys, got the Guru error again.
I'm baffled.
Re: FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 13. Nov 2022, 18:22
by scottgus1
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab.
Re: FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 13. Nov 2022, 22:56
by Jim Comfort
Here's my vbox log. The Guru Meditation section shows up about halfway down the scroll bar.
Jim
Re: FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 14. Nov 2022, 02:27
by scottgus1
RAM is overprovisioned, but I'm not certain if this would cause the problem right away:
00:00:09.711828 Host RAM: 7391MB (7.2GB) total, 2812MB (2.7GB) available
00:00:10.838502 RamSize <integer> = 0x00000000f0000000 (4 026 531 840, 3.7 GiB)
00:00:10.838888 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128.0 MiB)
This is the guru meditation:
00:00:22.293999 HM: VERR_VMX_INVALID_GUEST_STATE:
00:00:22.294018 HM: CPU[0] HM error = 0x23a
00:00:22.294034 HM: CPU[0] Guest-intr. state = 0x0
00:00:22.294104 HM: VERR_VMX_INVALID_GUEST_STATE:
00:00:22.294113 HM: CPU[1] HM error = 0x0
00:00:22.294122 HM: CPU[1] Guest-intr. state = 0x0
00:00:22.294133 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:00:22.294150 Console: Machine state changed to 'Stuck'
00:00:22.294488 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:22.294489 !!
00:00:22.294489 !! VCPU0: Guru Meditation -4014 (VERR_VMX_INVALID_GUEST_STATE)
Curious the error happens in VMX, which I think has something to do with VT-x. Maybe a host service or app (like 3rd-party AV) stole VT-x from Virtualbox?
I have a vague recollection Core 2 CPUs had some issue but I may be wrong:
00:00:13.959344 Full Name: "Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz"
However, this is interesting:
Jim Comfort wrote:I recently upgraded VBox to 7.02
If you can go back to your previous version and the VM comes back, then this could be a 7.0 bug. A log from 6.1.something, 6.1.40 preferably, with the VM running well, may be helpful to the gurus.
Re: FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 14. Nov 2022, 11:43
by fth0
The VERR_VMX_INVALID_GUEST_STATE error with state VMX_IGS_V86_GS_LIMIT_INVALID (0x23a) is a very low level issue. It could be a race condition of some kind, because I'd normally expect the FS limit check to fail before the GS limit check.
I'd suggest to create a ticket in the
Bugtracker.
Re: FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 14. Nov 2022, 23:22
by Jim Comfort
Oddly enough, this problem is only occurring on my BSD VM's. And the workaround is to hit any key after the VM BIOS boots and before the BSD options screen comes up. For some reason, hitting any key interrupts things before it can throw an error. When I just try letting them boot, I get the fatal error every time, no matter how I shut down my VM.
Oh, and it also happens on a new machine I tried setting up right after my upgrade. And the workaround works on it, too.
Jim
Re: FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 14. Nov 2022, 23:26
by fth0
It's the nature of race conditions to be very timing sensitive.
Re: FreeBSD 13.1-RELEASE on VBox 7.02
Posted: 25. Feb 2023, 09:08
by Jim Comfort
Just an update. I upgraded to 7.06 and the problem has disappeared.
Thanks, guys!