I followed step by step on this documentation (https://www.kali.org/docs/virtualizatio ... -guest-vm/). And I got the error below when I choose Kali as start-up disk. I noticed the documentation has .iso file but the file I downloaded from their site is the .ova file. (https://www.kali.org/get-kali/#kali-virtual-machines)
What caused this problem and how do I fix this?
VirtualBox VERR_NOT_SUPPORTED Kali VM
VirtualBox VERR_NOT_SUPPORTED Kali VM
Last edited by mpack on 29. Mar 2022, 09:55, edited 1 time in total.
Reason: Replace image with local attachment
Reason: Replace image with local attachment
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VirtualBox VERR_NOT_SUPPORTED Kali VM
An ISO allows you to create a VM and install an OS from scratch.
If you have an OVA then somebody else already created the VM and installed the OS and exported it as an OVA appliance. All you need to do is import the VM using the File|Import... function of the VirtualBox Manager.
The only problem with importing an OVA is that you have to assume that the original guy did a good job, sensible settings etc. They often do not. Also the OVA will either be generic (lowest common denominator) or will be tuned for the originators PC, so you should check the settings to make sure they are suitable for your PC. Especially regarding the usage of RAM, graphics RAM and number of CPU cores.
You'll have a choice during import about whether you want to import the disks in VMDK or VDI format. I suggest VDI format, which is the native format in VirtualBox and hence the best supported one.
If you have an OVA then somebody else already created the VM and installed the OS and exported it as an OVA appliance. All you need to do is import the VM using the File|Import... function of the VirtualBox Manager.
The only problem with importing an OVA is that you have to assume that the original guy did a good job, sensible settings etc. They often do not. Also the OVA will either be generic (lowest common denominator) or will be tuned for the originators PC, so you should check the settings to make sure they are suitable for your PC. Especially regarding the usage of RAM, graphics RAM and number of CPU cores.
You'll have a choice during import about whether you want to import the disks in VMDK or VDI format. I suggest VDI format, which is the native format in VirtualBox and hence the best supported one.