Hello,
I encounter the following problem: Ubuntu 20.04 no longer starts in VM.
A few days ago, it worked without problems, but it doesn't start today.
When I turn it on, the screen turns on and off for 30 seconds and then the error appears: "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again."
I tried to update Ubuntu, but it still doesn't start.
I mention that I haven't changed anything since the day Ubuntu started and until today when it doesn't work.
Can anyone help me solve the problem ?
Thanks
Ubuntu 20.04 no longer starts in VM
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Ubuntu 20.04 no longer starts in VM
Sure. First, we move this to a forum more tuned to fixing things than "Suggestions"Zlotea Catalin wrote:Can anyone help me solve the problem ?
Start the VM from full power off, not save-state. Run until you see the problem happen, then shut down the VM from within the VM OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Please right-click the VM in the main Virtualbox window's VM list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.
-
- Posts: 6
- Joined: 5. Mar 2021, 18:51
Re: Ubuntu 20.04 no longer starts in VM
Now when I tried to start Ubuntu it just turned on and off the screen and I didn't get any more errors.
I turned off Ubuntu with the Power Off option.
I am attaching the VBox.log file.
I turned off Ubuntu with the Power Off option.
I am attaching the VBox.log file.
- Attachments
-
- VBox.rar
- (27.75 KiB) Downloaded 114 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Ubuntu 20.04 no longer starts in VM
Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)
-
- Posts: 6
- Joined: 5. Mar 2021, 18:51
Re: Ubuntu 20.04 no longer starts in VM
Thank you !
Now Ubuntu is running again.
But so far why went with Hyper-V enabled ?
Now Ubuntu is running again.
But so far why went with Hyper-V enabled ?
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Ubuntu 20.04 no longer starts in VM
That is a good question, I don't know. Maybe Microsoft pushed an update and changed something.
-
- Posts: 6
- Joined: 5. Mar 2021, 18:51
Re: Ubuntu 20.04 no longer starts in VM
I understand.
Thanks again for the help.
Thanks again for the help.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Ubuntu 20.04 no longer starts in VM
Glad you're up and running!
Re: Ubuntu 20.04 no longer starts in VM
Hi, I have the same problem but it seems the reason is not Hyper-V being enabled. Can you take a look?scottgus1 wrote:Glad you're up and running!
- Attachments
-
- seed-ubuntu20.04 Secret-errorlog.zip
- error log
- (39.97 KiB) Downloaded 15 times
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Ubuntu 20.04 no longer starts in VM
Hyper-v is Microsoft's VM software, and is never required by VirtualBox. In fact having Hyper-v enabled pretty much guarantees that the VirtualBox experience will be terrible.alluv wrote:the reason is not Hyper-V being enabled. Can you take a look?
Happily, your log shows that, indeed, Hyper-v is not enabled - so keep it up!
The only big error I see in a quick glance at your VM is that graphics RAM is very low at only 28MB. I would increase this to 128MB.
Also the VirtualBox Guest Additions pre-installed by your Ubuntu distro are quite out of date. You need to purge the Ubunto GAs fork and install the real thing (see chapter 4 of the user manual).
Also a warning: your host has 16GB RAM installed but only had 3GB free when the VM was launched. Not a problem so far (the VM is configured to use 2GB), but it concerns me that you have a monster RAM hog in there somewhere - keep an eye on it.