Ubuntu 22.04 kernel panic on install, Windows 10 host.

Discussions about using Linux guests in VirtualBox.
Post Reply
Zapados
Posts: 6
Joined: 21. Dec 2020, 09:54

Ubuntu 22.04 kernel panic on install, Windows 10 host.

Post by Zapados »

Ubuntu 22.04 kernel panic on install, Windows 10 host, VirtualBox 6.1.18.

I had an old Ubuntu VM that I updated to 22.04 and got a kernel panic on restart. I thought maybe something went wrong with the update, and I didn't need the contents of the VM that much, so I opted to a try a fresh install. When attempting the install, I get the error attached.

I attached the VirtualBox logs.

Has anyone else seen this with Ubuntu 22.04? Any thoughts on how I can get it fixed and up and running again?

I'm running any older version of VirtualBox as newer versions were having sound issues with a Windows 10 host, Windows 10 guest. If this is confirmed resolved now, I'd be open to updating.

Thank you for your time!
Attachments
Capture.PNG
Capture.PNG (25.1 KiB) Viewed 9288 times
Ubuntu_22.04-2023-11-07-15-25-13.rar
(26.42 KiB) Downloaded 188 times
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu 22.04 kernel panic on install, Windows 10 host.

Post by mpack »

This perhaps.
00:00:03.363533 Host RAM: 16174MB (15.7GB) total, 3713MB (3.6GB) available
...
00:00:03.550594 RamSize <integer> = 0x0000000100000000 (4 294 967 296, 4 096 MB, 4.0 GB)
Or this:
00:00:03.550847 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)
I also notice that your VirtualBox version is pretty ancient - 6.1.18. I hope that the Linux versions you install are at least equally ancient.
Zapados
Posts: 6
Joined: 21. Dec 2020, 09:54

Re: Ubuntu 22.04 kernel panic on install, Windows 10 host.

Post by Zapados »

Thank you mpack!

I worked through these one at a time as best as possible, and it appears that the "ancient VirtualBox" is what was killing me. Updated to the latest 6.x and the VM is working now! However, I'm in "turtle mode" but I think that's because this system is just a bit of a dog now...as you mentioned, RAM usage is tight.

Cheers!
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu 22.04 kernel panic on install, Windows 10 host.

Post by mpack »

Turtle mode is because you have Hyper-v enabled on the host, not because the host is old.
00:00:03.551088 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:03.608969 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
Hyper-v interferes and generally slows everything down. To get rid of it, see HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Zapados
Posts: 6
Joined: 21. Dec 2020, 09:54

Re: Ubuntu 22.04 kernel panic on install, Windows 10 host.

Post by Zapados »

Is there any way to explicitly check if HyperV is enabled?

This machine is run by corporate overlords. I have access to disabling HyperV in the "Windows features" and have done so. However I believe there are other aspects in that list I won't have permission to touch - Device Guard, bcdedit stuff, etc.
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Windows, Linux

Re: Ubuntu 22.04 kernel panic on install, Windows 10 host.

Post by scottgus1 »

Zapados wrote: 9. Nov 2023, 18:30 Is there any way to explicitly check if HyperV is enabled?
Two ways, both covered when carefully reading the "Attempting" tutorial linked above:
  1. If the green turtle is seen in the VM's Status Bar.
  2. If "HMR3Init: Attempting fall back to NEM:" is shown in the VM's log.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: Ubuntu 22.04 kernel panic on install, Windows 10 host.

Post by mpack »

Zapados wrote: 9. Nov 2023, 18:30 Is there any way to explicitly check if HyperV is enabled?
The easiest way is to look in the logs for those lines I quoted back to you.
Post Reply