Page 1 of 1
Guest Arch Linux crashes to Guru Meditation
Posted: 21. Jan 2018, 18:22
by b0nk
Hello.
After updating from 5.2.2 to 5.2.6 I can't get passed the syslinux boot selection screen.
When I select to boot the Arch System I see this
Code: Select all
Loading ../vmlinuz-linux... ok
Loading ../intel-ucode.img...ok
Loading ../initramfs-linux.img...ok
Probing EDD (edd=off to disable)... ok
Then it crashes.
Uploaded the log so I can get some help here.
Thank you.
Re: Guest Arch Linux crashes to Guru Meditation
Posted: 21. Jan 2018, 19:12
by socratis
00:00:06.011021 HM: HMR3Init: Falling back to raw-mode: VT-x is not available
You'll need to address this, most probably because something else is grabbing VT-x exclusively. Chances are it's Hyper-V, or something that uses Hyper-V, like antivirus, debuggers, other virtualizers, etc. The lack of VT-x is what leads your VM to a guru meditation:
00:00:20.197246 !! VCPU0: Guru Meditation -2403 (VERR_TRPM_DONT_PANIC)
Re: Guest Arch Linux crashes to Guru Meditation
Posted: 21. Jan 2018, 19:20
by b0nk
Ah VT-x. My CPU does not support that feature.
I suppose the kernel in the guest is doing something to request virtualbox some VT-x features?
Maybe if I try to downgrade to a previous virtualbox...
What do you think I should do?
Re: Guest Arch Linux crashes to Guru Meditation
Posted: 21. Jan 2018, 19:23
by socratis
I don't know what you should do, but if you say that 5.2.2 was working for you, you have the answer. Plus, I'd stay away from newer OSes and VirtualBox versions, as they they tend to ask for more and more hardware features to be present.
Re: Guest Arch Linux crashes to Guru Meditation
Posted: 22. Jan 2018, 13:58
by mpack
b0nk wrote:Ah VT-x. My CPU does not support that feature.
In that case I'd suggest turning off that feature in the VM settings. I believe that VirtualBox now treats it as an error to be asked to enable features which the host doesn't support.
Unfortunately, you may find that the feature is grayed out in the VM settings precisely because your host doesn't support it. For that reason you may have to disable it using a VBoxManage command line on the host :-
Code: Select all
VBoxManage <vm name or UUID> modifyvm --hwvirtex off