Kali-Linux in VirtualBox -- Reboot Failed after Installation?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kali-Linux in VirtualBox -- Reboot Failed after Installation?
So guys, I'm rather new at this, but I'm finding Linux very interesting and fun to learn about. I was trying to run Kali-Linux as a virtual machine using Oracle VirtualBox, and I got to the part where it asks you if you would like to install the GRUB Boot loader. I chose yes, then it starts "finishing the installation." I believe it is running "remove-live-packages" at this point. It starts to reboot, then it gets to the point where it says "Decompressing Linux..." Then, I get an error message explaining how to pull up the log.
I'm not entirely sure if this is the right forum to go to with this problem, but I'm hoping you guys can point me in the right direction, if it's not. Anyways, here's the log. (The log is WAY larger than the character limit, so I just stuck as much of the end as I could on here. Is there a better way to do it?)
Code:
01:03:48.746712 /SELM/UpdateFromCPUM/AlreadyStaleCS 0 times
01:03:48.746718 /SELM/UpdateFromCPUM/AlreadyStaleDS 0 times
01:03:48.746724 /SELM/UpdateFromCPUM/AlreadyStaleES 0 times
01:03:48.746730 /SELM/UpdateFromCPUM/AlreadyStaleFS 0 times
01:03:48.746736 /SELM/UpdateFromCPUM/AlreadyStaleGS 0 times
01:03:48.746742 /SELM/UpdateFromCPUM/AlreadyStaleSS 0 times
01:03:48.746748 /SELM/UpdateFromCPUM/DetectedStaleCS 0 times
01:03:48.746754 /SELM/UpdateFromCPUM/DetectedStaleDS 0 times
01:03:48.746760 /SELM/UpdateFromCPUM/DetectedStaleES 0 times
01:03:48.746766 /SELM/UpdateFromCPUM/DetectedStaleFS 0 times
01:03:48.746772 /SELM/UpdateFromCPUM/DetectedStaleGS 0 times
01:03:48.746778 /SELM/UpdateFromCPUM/DetectedStaleSS 0 times
01:03:48.746784 /SELM/UpdateFromCPUM/StaleToUnstale 0 times
01:03:48.746790 /TM/CPU/00/cNsExecuting 1881988728941 ns
01:03:48.746796 /TM/CPU/00/cNsHalted 1293636437062 ns
01:03:48.746803 /TM/CPU/00/cNsOther 484318379060 ns
01:03:48.746809 /TM/CPU/00/cNsTotal 3659943545063 ns
01:03:48.746815 /TM/CPU/00/cPeriodsExecuting 62024685 count
01:03:48.746821 /TM/CPU/00/cPeriodsHalted 60321 count
01:03:48.746828 /TM/CPU/00/pctExecuting 99 %
01:03:48.746834 /TM/CPU/00/pctHalted 0 %
01:03:48.746840 /TM/CPU/00/pctOther 0 %
01:03:48.746846 /TM/CPU/pctExecuting 99 %
01:03:48.746852 /TM/CPU/pctHalted 0 %
01:03:48.746858 /TM/CPU/pctOther 0 %
01:03:48.746864 /TM/MaxHzHint 0 Hz
01:03:48.746870 /TM/R3/1nsSteps 347578 times
01:03:48.746877 /TM/RC/1nsSteps 75256 times
01:03:48.746883 /TM/TSC/offCPU0 0 ticks
01:03:48.746889 /TM/VirtualSync/CurrentOffset 0 ns
01:03:48.746895 /VUSB/0/cUrbsInPool 0 count
01:03:48.746902 /VUSB/1/cUrbsInPool 1 count
01:03:48.746908 ********************* End of statistics **********************
01:03:48.799993 NAT: zone(nm:mbuf_cluster, used:0)
01:03:48.800458 NAT: zone(nm:mbuf_packet, used:0)
01:03:48.800478 NAT: zone(nm:mbuf, used:1)
01:03:48.800508 NAT: zone(nm:mbuf_jumbo_pagesize, used:0)
01:03:48.800924 NAT: zone(nm:mbuf_jumbo_9k, used:0)
01:03:48.801174 NAT: zone(nm:mbuf_jumbo_16k, used:0)
01:03:48.801308 NAT: zone(nm:mbuf_ext_refcnt, used:0)
01:03:49.011772 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
01:03:51.220851 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is being powered down}, preserve=false
01:03:51.266274 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Invalid machine state: PoweredOff (must be Running, Paused or Stuck)}, preserve=false
The end makes me think there's something weird going on with VirtualBox, but I'm not sure.
As the distribution developers, one would likely expect us to recommend that everyone use Kali Linux. The fact of the matter is however, that Kali is a Linux distribution specifically geared towards professional penetration testing and security auditing and as such, it is NOT a recommended distribution for those unfamiliar with Linux.
In addition, misuse of security tools within your network, particularly without permission, may cause irreparable damage and result in significant consequences.
Hi Josh1313, to fix the issue, you need only to go to the settings of your Kali VM --> system --> processor --> check Enable PAE/NX
If it does not work, try enabling/disabling other options in Motherboard.
For Josh VV, you were not helpful with your rude post.
Hi Josh1313, to fix the issue, you need only to go to the settings of your Kali VM --> system --> processor --> check Enable PAE/NX
If it does not work, try enabling/disabling other options in Motherboard.
For Josh VV, you were not helpful with your rude post.
*necromancer chanting*
Since I ran into this problem too, and the OP didn't respond or label this "Solved", I will. This solution worked for me.
(If it matters, I don't think Josh was rude, but unhelpful, yes. I need this for class.)
I loaded up Kali in a VM just for grins and giggles and it failed after reboot because VirtualBox's default 8 GB HDD for Linux was not enough to accommodate Kali and all the included tools. There was a quick boot message just before failure to the effect that there wasn't enough space; I caught the message on the second try.
I removed the VM, increased the virtual HDD size to 12 GB, and it ran fine. The actual size of the dynamic *.vdi file is slightly over 8 GB.
I loaded up Kali in a VM just for grins and giggles and it failed after reboot because VirtualBox's default 8 GB HDD for Linux was not enough to accommodate Kali and all the included tools. There was a quick boot message just before failure to the effect that there wasn't enough space; I caught the message on the second try.
I removed the VM, increased the virtual HDD size to 12 GB, and it ran fine. The actual size of the dynamic *.vdi file is slightly over 8 GB.
hello,
i have the same problem but I followed this process which worked for me. and i am running kali linux on virtualbox smoothly
source: install kali linux on virtualbox
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
