haii,
i was just opening linux through virtualbox but it came as critical error occured whili running virtual machine. A dialogue box appeared showing that error happened,it says to upload 2 files..I request you to help to fix this problem.
[Mod edit; removed completely black screenshot. We all know what black looks like...]
Critical error running Kali Linux
-
- Volunteer
- Posts: 1631
- Joined: 25. May 2010, 23:48
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation
Re: A critical error has occurred while running the virtual machine
@raghs - whilst the symptoms of your problem and potentially the causes may be similar to the OP you don't have a Linux host but are running Windows. The topic had also previously been marked as solved. Hopefully one of the admins / mods will move your question and my answer to a new thread in the correct place.
-Andy.
You have allocated memory to the guest that you don't have available on the host. Your options are: a) allocate less memory to the guest, b) close some applications on the host, or c) buy some more memory for the host.VBox.log wrote:00:00:01.787455 Host RAM: 1911MB total, 470MB available 00:00:02.105354 RamSize <integer> = 0x0000000020000000 (536 870 912, 512 MB) 00:00:02.105698 VRamSize <integer> = 0x0000000001000000 (16 777 216, 16 MB)
You need to enable this in the motherboard / PC / laptop BIOS. Your Intel i3 550 CPU supports it. See your PC's manufacturer help on how to do this. Also, make sure that nothing else has an exclusive hold on the VT-x.VBox.log wrote:00:00:02.105894 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes
-Andy.
My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
Please don't ask me to do your homework for you, I have more than enough of my own things to do.
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Critical error running Kali Linux
I split the above two posts off to a new topic in a more appropriate forum.
I doubt that "Linux 2.6" is the correct template to use for Kali Linux. According to my research, Kali is based on Debian.
A split2g vmdk! A long time since I've seen that. 21 segments plus the descriptor - and no need for it that I can see, as the host filesystem is NTFS and can easily handle files larger than 2GB. I would suggest cloning this VM to a fully native VirtualBox form soon.
I doubt that "Linux 2.6" is the correct template to use for Kali Linux. According to my research, Kali is based on Debian.
A split2g vmdk! A long time since I've seen that. 21 segments plus the descriptor - and no need for it that I can see, as the host filesystem is NTFS and can easily handle files larger than 2GB. I would suggest cloning this VM to a fully native VirtualBox form soon.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Critical error running Kali Linux
I'll simply sticking to this:
With that amount of RAM, and the kind of host that you're running, it's going to be really tough to get anything except DOS, Win3.1, or Win98 running (or similar). Kali itself requires 1024 MB (if not more) to function appropriately. It's not a "light" OS, either RAM-wise or HD-wise.00:00:01.742422 OS Product: Windows 8.1 00:00:01.787455 Host RAM: 1911MB total, 470MB available
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.