virtualbox.org

Hello! I got this problem when i'm installing kali ,i tried with VMware and it's passing that error .Can anybody help me please ? I don't know to read the logs .

Start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log.

Search the log for the text:
HMR3Init: Attempting fall back to NEM:
If you find this text, and a note that VT-X or AMD-V is not available, then you might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate or crash. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon () will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. Look into I have a 64bit host, but can't install 64bit guests, 2nd post, points 2 & 3 and ensure that none of these things are running.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

Your Virtualbox should be running now. If the green turtle still appears and the tell-tale lines are in the log, try all the steps again. If you don't get the standard virtualization icon, post back exactly what you did and we'll try to help some more.

For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

If you don't find this above text, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

(just to show this tread as updated: Logs were attached to the opening post)

Thanks, Martin, for for showing about the updated post!

Hunt3r, you have the suspect line in the vbox.log. Follow the posted instructions to shut off Hyper-V.

Thank you for your post ,i followed all the stepts and it worked install kali but after instalation i restart and the virtual machine doesn't start ,all i can see it's black.

Please post a new vbox.log with the guest as it is performing now.

BTW, please post in new posts not by editing old ones, as edits don't show up in the email reports that we get when someone posts.

Here there are .

Everything seems copacetic in the new log, AMD-V is fully available, so Hyper-V is off, good.

Only thing is:

00:00:10.116351 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:01:44.544318 Changing the VM state from 'RUNNING' to 'SUSPENDING'

The process touches the hard disk then does absolutely nothing until the Virtualbox window is closed.

You'll need to put the Kali ISO in and reinstall.

I managed it to made it work ,i think the problem was when i tried to install without grab loader or i forgot to mention ,got installed kali linux in windows store with wls 2(i deleted it) .I saw that without hypervisior it didn't want to start .How will affect windows with other programs or games if hypervisior is off ?

If 'hypervisior' means Hyper-V, your Windows will still run fine. I run all my Windows 10 hosts without Hyper-V. I don't know how other programs or games will work with or without Hyper-V.

FWIW both Virtualbox and Hyper-V are hypervisors, as well as VMware, Xen, KVM, Fusion, etc.

I cannot understand your last post. Did you decide to use WSL2? That's fine if you did, we'll just need to know if any other help is required.

Before instaling virtual box i was using kali with wsl2 ,but i didn't succeed to install ubuntu with gui so i wanted to change to virtual box . Now i use kali with virtual box ,it's working fine .Before ,when i was installing kali i chose no for grab loader and the os didn't boot or maybe it was something tied to installed kali on wls2 . Can i use " bcdedit /set hypervisorlaunchtype auto " - maybe windows will choose itself (for virtual box no or yes for wsl 2 ).Thank you for your help.

Ok, I get you now.

Hunt3r wrote:Can i use " bcdedit /set hypervisorlaunchtype auto " - maybe windows will choose itself

No this won't work. Hyper-V needs to be enabled before Windows 10 boots, it can't be turned on/off on the fly.

The 'tenforums' link above shows a boot switch that can be used after the computer turns on but before Windows 10 starts to manually choose to run Hyper-V/WSL2 or no Hyper-V for Virtualbox.

I understand . Thank you for everthing.

Glad you're up and running! If you have any more trouble, please let us know.