virtualbox.org

Kali linux-2020-06-25-17-56-02.log file wrote:

00:00:02.406620 VMSetError: Implementation of the USB 2.0 controller not found!
00:00:02.406621 Because the USB 2.0 controller state is part of the saved VM state, the VM cannot be started. To fix this problem, either install the 'Oracle VM VirtualBox Extension Pack' or disable USB 2.0 support in the VM settings.
00:00:02.406621 Note! This error could also mean that an incompatible version of the 'Oracle VM VirtualBox Extension Pack' is installed

The "Kali linux-2020-06-25-17-56-02.log" file clearly indicates the problem and the possible solutions in the lines quoted above.

The hardening log ends in an exit code of 0, meaning that there were no hardening problems for this run, which does not match the png error screenshot. It is important to post logs that actually correspond to the error message.

Regarding fth0's post about the vbox.log's error that the USB2 has a problem, The vbox.log also shows no extension pack installed. The extension pack provides USB2 support, among other things. Install the 6.0.22 Extension Pack.

The log's error also mentions a saved state, though the status says the guest is 'starting' not 'restoring'. If you get the Extension Pack installed, and still the guest will not start, right-click the guest in the guest list and choose Discard Saved State.

scottgus1 wrote:The log's error also mentions a saved state, though the status says the guest is 'starting' not 'restoring'. If you get the Extension Pack installed, and still the guest will not start, right-click the guest in the guest list and choose Discard Saved State.

I could imagine that the "saved VM state" in the log message refers to the .vbox file configuring USB 2.0 (instead of a saved state of the VM).

Regarding the error screenshot: It complains about the kernel driver not being the same version as VirtualBox. A full uninstall, reboot and install sequence may be necessary (especially the reboot part ).

I have disabled Controller from VM's settings and then I checked all my VMs work. So I reinstalled my Extension_pack (Good version one 6.0.20).

I checked and the result is the problem is solved but I don't know what will happen if I update to 6.1.10 version of VirtualBox!

POuria25 wrote:the problem is solved

Excellent! Glad you're up and running.

POuria25 wrote:I don't know what will happen if I update to 6.1.10 version of VirtualBox!

Neither do we.

Always consider if you need to upgrade. "If it ain't broke don't fix it." When an upgrade is required, remove the Extension Pack too and install the matching Extension Pack for the Virtualbox version you are trying. If your Virtualbox guests are important, back them up before changing versions. In fact you should back up the whole host PC just in case. (You should be doing this anyway, backups are as ubiquitous as the internet and electricity.) And don't change to the newest version automatically. Read the forums to see if there is a big problem with a version before trying it. And keep the installer and Extension Pack files for the previous version so you can go back if you need to.