Critical Errors on Ubuntu Machine Boot

Discussions related to using VirtualBox on Windows hosts.
Post Reply
adarr
Posts: 3
Joined: 2. May 2022, 19:45

Critical Errors on Ubuntu Machine Boot

Post by adarr »

On startup, I get "A critical error has occurred while running an Ubuntu virtual machine and the machine execution has been stopped." As instructed by the rest of the message, I have attached my logs here (zipped since I ran into file size issues when trying to attach) and am seeking help. I am not sure what prompted this crash, last Power Off several days ago went normally. This is the first time something like this has happened, so unfortunately that also means I have no backup (lesson learned!).
Attachments
Logs.zip
(58.2 KiB) Downloaded 2 times
VBox.png
VBox.png (993 Bytes) Viewed 959 times
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: Critical Errors on Ubuntu Machine Boot

Post by scottgus1 »

00:00:01.981947 HM: HMR3Init: AMD-V w/ nested paging
00:00:02.689711 Console: Machine state changed to 'GuruMeditation'
00:00:02.689850 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:02.689850 !!
00:00:02.689850 !! VCPU0: Guru Meditation -4054 (VERR_SVM_IN_USE)
Looks like something is taking SVM away from Virtualbox. Probably your 3rd-party antivirus. Check it for a 'hardware virtualization' setting and turn the setting off.
adarr
Posts: 3
Joined: 2. May 2022, 19:45

Re: Critical Errors on Ubuntu Machine Boot

Post by adarr »

I will try this if the bug reappears...I forgot the first rule of IT, "Did you turn your computer on and off again?" so a simple restart of Windows fixed the virtual bootup. Thank you for your help, if the fix helps in the future I'll reply here again for posterity.
adarr
Posts: 3
Joined: 2. May 2022, 19:45

Re: Critical Errors on Ubuntu Machine Boot

Post by adarr »

Bug reappeared after several hours of operation; disabled hardware virtualization and restarted Windows, error has not reappeared.
Post Reply