virtualbox.org

I am using vagrant (I know vagrant itself is not supported, but it seems to be a problem with the virtualbox itself) with virtualbox and everything worked fine. Then I had a PHP
loop (for some debugging) which got the machine stuck. I used vagrant halt to stop it. Now when I want to start the machine again (doesnt matter if I use vagrant up or directly inside the Oracle VM Virtual Box) I receive a Kernel panic - not syncing: Attempted to kill init! error. The log from VM is attached. Any help is appreciated, since I need this VM to work

Host hyper-V is enabled. You have two options:

1. Try the 6.1.35 test build; it's reported to do better with active host Hyper-V. Save the test build installer until you update again later. You'll need it if your host's MSI installation database goes south (they do) and the installer will not be available for download after the next even-number version gets released.

2. Turn off Hyper-V. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

scottgus1 wrote:Host hyper-V is enabled. You have two options:

1. Try the 6.1.35; it's reported to do better with active host Hyper-V. Save the test build installer until you update again later. You'll need it if your host's MSI installation database goes south (they do) and the installer will not be available for download after the next even-number version gets released.

2. Turn off Hyper-V. See.

2. Seems to work! After turning it off and restarting, everything went back to work!

Are there any disadvantages in turning hypervisorlaunchtype off? Or maybe a positive side? Not sure if it's just a feeling, but the VM seems to be a little bit faster?

Hyper-V itself is a hypervisor, a type-1 that touches the hardware even before the host OS. So your Windows host itself is a VM when Hyper-V is running. Then Virtualbox, a type-2 hypervisor which must run in the host OS, is now running as nested virtualization. So Virtualbox under Hyper-V will be slower.

The devs continue to work on better Virtualbox with Hyper-V enabled. Every time Microsoft changes something in their Hyper-V, the devs have to recalculate for the new arrangement. The 6.1.35 test build is the latest recalculation taking new Hyper-V changes into account that works according to some forum gurus.

Microsoft is basing a great deal of new security and function features on Hyper-V. With Hyper-V disabled, all of those features can't run. Whether one needs those features or faster Virtualbox is a decision each user or IT department will have to make. (Heaven help Microsoft if some deep Meltdown/Spectre-like security hole in Hyper-V gets discovered several years from now...)

I was getting the same issue also while trying to boot Oracle Linux on Virtual Box.

Solve it by getting an older ISO version. Allocate more CPU cores also and see if it works(at least two).

G Ngeno wrote:at least two

Two is actually best, until 3rd-party multi-processor-aware programs are installed in the VM. More than 2 slows down the VM due to extra scheduling oversight required on the host. Many OS's love 2 processors in a VM.

G Ngeno wrote:Allocate more CPU cores also and see if it works(at least two).

In general, adding resources to see if it works is a poor approach. It's basically thrashing. The VM should be allocated the resources it needs, no more and no less.

Likewise "get an older ISO" is more thrashing. How old does it need to be? It may be that a certain version of Linux has trouble booting in a certain version of VirtualBox, so that can best be pinned down if you give a specific VirtualBox version of the version of the OS you are trying to install.