Next, you need to select the hard disk file type as “ VDI (VirtualBox Disk Image)” and the storage as “ Dynamically allocated,” as shown in the image above. If you want to allocate the whole size at the beginning itself, you can check the Pre-allocate Full Size check box. Also, memory allocation is set to dynamic by default. Hard disk file type will be VDI (VirtualBox Disk Image) by default. Allocate hard disk space to virtual machine The installation should not be a problem with the minimum allocated size (8 GB), but to be on the safe side, you may want to allocate at least 10-15 GB. In order to set the hardware parameters, you need to check the create a virtual hard disk now box. Step 3: You can choose a preferred location path for the virtual hard disk and tweak the size as per your requirements. Now, proceed to set the virtual hard disk size. Provide RAM and CPU cores for the virtual machine (On the newer versions of VirtualBox, this option comes under the next step). It should be the selected option by default. In my case, I allocate ~ 3 GB of RAM and 2 processor cores.Īlso, make sure to create a virtual hard disk under the “Hard disk” option. If it is just for minor testing, you can go ahead with the default setting. You should increase the memory size to use the virtual machine comfortably. On newer VirtualBox versions, you can select the ISO file from here itself. Step 2: Enter the name of your virtual machine, it should auto-detect the “Type” and “Version” respectively when you type in “ Arch Linux” in the name field. Hence, I recommend using the expert mode to create the virtual machine.įret not, the expert mode is as easy, with just a bit of extra available options and nothing else to worry about. Select Expert Mode in New Machine dialog box Note that you can continue creating the virtual machine using the guided mode, but you get more options at a single glance with the expert mode. Select New button to create a new virtual machine
![virtual optical disk file download virtual optical disk file download](https://teaching.idallen.com/cst8207/15w/notes/data/virtualbox_image5.png)
Launch VirtualBox and click on “ New” to create a virtual machine. Step 1: First, you need to set up a few things in VirtualBox. Now, let us begin installing Arch Linux on VirtualBox. Hold on to the ISO file when needed you can delete it to free space on your system after successful installation. You should find options to download using torrent or download the file directly. Once done, you need to head to Arch Linux’s official website to download the ISO file. Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE).ĪMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).If you are using Windows 10 or a newer version, please ensure that virtualization is enabled on your system. i also have not taken any steps yet to fix this problem. I don't have hardware virtualization enabled that I know of and haven't heard of it. I have not installed Host Extensions & Guest Additions. What is this optical drive and how do I set this up and why would I have to touch the BIOS settings?
![virtual optical disk file download virtual optical disk file download](https://i.imgur.com/EFDd4cq.png)
I have only ever had to choose an os as the last step in setting up a VirtualBox VM in my experience. "Please select a virtual optical disk file or a physical optical drive containing a disk to start your machine from."
![virtual optical disk file download virtual optical disk file download](https://www.softwareok.com/img/faq/Windows-8/create_a_virtual_hard_disk_on_Windows_8.1_and_10_2015-03-08-14-02-26.png)
After having downloaded the virtual machine image and selected it for the os to install this is the message I get with an error following after I am unable to choose an optical drive.
![virtual optical disk file download virtual optical disk file download](https://www.wintips.org/wp-content/uploads/2013/01/image16.png)
The problem that I have run into is with the optical drive and some BIOS settings that I will reveal below. I am on windows, I came from FreeBSD and it seems like VirtualBox works a little differently here.