- VBox.zip
- Log file
- (27.88 KiB) Downloaded 7 times
Kali hangs trying to start
Kali hangs trying to start
I installed Kali Linux in a Virtualbox VM. It ran fine for a couple of months then started coming up to the Kali Linux logo and hang there. It is Virtualbox 6.1.18 and Kali 2021.1. I had installed Kali on a laptop, same version and it works fine.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Kali hangs trying to start
Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).
Re: Kali hangs trying to start
I checked and dont have HyperV set. See Image. I looked through the log file and dont find the text the other post was talking about. I must be overlooking something. I will add the log file in a response to the post.
Re: Kali hangs trying to start
I am attaching the log file after running the commands in the recommended post.
- Attachments
-
- VBox.zip
- (28.18 KiB) Downloaded 10 times
Re: Kali hangs trying to start
I have Windows XP running in a Virtualbox VM and it loads fine. Kali also runs fine on my laptop. I deleted the old Kali VM, created a new one and loaded Kali and it does the same thing.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Kali hangs trying to start
cyberbum wrote: I looked through the log file and dont find the text the other post was talking about
Looks like you'll need to bone up on that search function.the second posted log wrote:00:00:02.922783 HM: HMR3Init: Attempting fall back to NEM: AMD-V is not available
Hyper-V is still enabled.
the NEM tutorial wrote:If you don't get the standard virtualization icon, post back exactly what you did and we'll try to help some more.
Re: Kali hangs trying to start
I finally got it working. This is Windows 10 Pro. I did all your suggestions. Everything showed Hyper-V was not running. I think I remember turning on Memory integrity under Core Isolation. What could that hurt? Ha Ha That seems to be it.
It is working again. I turned it Off.
It is working again. I turned it Off.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Kali hangs trying to start
Great! Glad you're up and running.
Re: Kali hangs trying to start
My Kali was working fine April 14. I upgraded Virtualbox to version 6.1.22 r144080 and it trys to come up but gets a screen that says "Oh no! Something has gone wrong." I try to run OpenVAS Ubuntu and it gets a VIrtualBoxVM.exe application error.
- Attachments
-
- Oh_No_Picture.png (16.03 KiB) Viewed 2388 times
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Kali hangs trying to start
Your Hyper-V is back on.
Search for that special text first before posting a problem. If you find it, then turn Hyper-V off per the posted tutorial, then try the VM again.
Search for that special text first before posting a problem. If you find it, then turn Hyper-V off per the posted tutorial, then try the VM again.
Re: Kali hangs trying to start
The problem I have had is it not showing it HyperV is running. I have followed your instructions about turning it off from the command line and it didnt change anything. I will try again. I am surprised that the UBuntu VM is crashiing now and it didnt before I upgraded VirtualBox.
Re: Kali hangs trying to start
When I tried running the commands to turn off HyperV I get the message in the screenshot.
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Kali hangs trying to start
The DISM command may have failed because 'Hyper-V' could be off, and it may not be necessary. Continue with the tutorial steps.
Other things may have happened when your Virtualbox was upgraded, such as a Windows update.
Other things may have happened when your Virtualbox was upgraded, such as a Windows update.