Download Linux Os For Oracle Virtualbox

• Best Linux For Virtualbox
• Oracle Vm Virtualbox Download
• Download Linux Os For Oracle Virtualbox Free

Zorin OS is an Ubuntu based Linux distribution specially made for people new to Linux, people moving from Windows and macOS to Linux. Zorin OS 15 is the latest version of Zorin OS at the time of this writing. In this article, I am going to show you how to install Zorin OS 15 on VirtualBox. Linux Mint distribution is based on Ubuntu, it offers more complete out-of-the-box experience by including useful stuff like browser media codecs, DVD playback, plugins for browser, Java and other components. The purpose of Linux Mint is to produce a modern, elegant and comfortable operating system which is both powerful and easy to use. Download VirtualBox from its website and install it by double-clicking on the downloaded file. Ubuntu 18.10 Virtualbox Image Google Drive: Download Link Google Drive (back up): Download Link This image is fresh and clean ready for use, before using this Ubuntu OS you'll need to firstly create an account. Guest Tool from VirtualBox is installed. Oracle VirtualBox helps to run multiple OS at the same time on a single Computer Desktop or Laptop.VirtualBox is based on Virtualization technology, when you install a new Guest OS (Operating System) in the VirtualBox, then all the operating system files install inside a Virtual Disk Image (VDI) or Virtual Hard Drive (VHD), so it doesn't mess another operating system files into main OS.

For the various versions of Linux that are supported as host operating systems, see Section 1.4, 'Supported Host Operating Systems'.

You may need to install the following packages on your Linux system before starting the installation. Some systems will do this for you automatically when you install Oracle VM VirtualBox.

• Qt 5.3.2 or later. Qt 5.6.2 or later is recommended.

• SDL 1.2.7 or later. This graphics library is typically called libsdl or similar.

These packages are only required if you want to run the Oracle VM VirtualBox graphical user interfaces. In particular, VirtualBox, the graphical VirtualBox Manager, requires both Qt and SDL. If you only want to run VBoxHeadless, neither Qt nor SDL are required.

In order to run other operating systems in virtual machines alongside your main operating system, Oracle VM VirtualBox needs to integrate very tightly with your system. To do this it installs a driver module called vboxdrv into the system kernel. The kernel is the part of the operating system which controls your processor and physical hardware. Without this kernel module, you can still use the VirtualBox Manager to configure virtual machines, but they will not start.

Network drivers called vboxnetflt and vboxnetadp are also installed. They enable virtual machines to make more use of your computer's network capabilities and are needed for any virtual machine networking beyond the basic NAT mode.

Since distributing driver modules separately from the kernel is not something which Linux supports well, the Oracle VM VirtualBox install process creates the modules on the system where they will be used. This means that you may need to install some software packages from the distribution which are needed for the build process. Required packages may include the following:

• GNU compiler (GCC)

• GNU Make (make)

• Kernel header files

Also ensure that all system updates have been installed and that your system is running the most up-to-date kernel for the distribution.

The running kernel and the kernel header files must be updated to matching versions.

The following list includes some details of the required files for some common distributions. Start by finding the version name of your kernel, using the command uname -r in a terminal. The list assumes that you have not changed too much from the original installation, in particular that you have not installed a different kernel type.

• With Debian and Ubuntu-based distributions, you must install the correct version of the linux-headers, usually whichever of linux-headers-generic, linux-headers-amd64, linux-headers-i686 or linux-headers-i686-pae best matches the kernel version name. Also, the linux-kbuild package if it exists. Basic Ubuntu releases should have the correct packages installed by default.

• On Fedora, Red Hat, Oracle Linux and many other RPM-based systems, the kernel version sometimes has a code of letters or a word close to the end of the version name. For example 'uek' for the Oracle Unbreakable Enterprise Kernel or 'default' or 'desktop' for the standard kernels. In this case, the package name is kernel-uek-devel or equivalent. If there is no such code, it is usually kernel-devel.

• On some SUSE and openSUSE Linux versions, you may need to install the kernel-source and kernel-syms packages.

If you suspect that something has gone wrong with module installation, check that your system is set up as described above and try running the following command, as root:

If you are running on a system using UEFI (Unified Extensible Firmware Interface) Secure Boot, you may need to sign the following kernel modules before you can load them:

• vboxdrv

• vboxnetadp

• vboxnetflt

• vboxpci

See your system documentation for details of the kernel module signing process.

Oracle VM VirtualBox is available in a number of package formats native to various common Linux distributions. See Section 1.4, 'Supported Host Operating Systems'. In addition, there is an alternative generic installer (.run) which you can use on supported Linux distributions.

Download the appropriate package for your distribution. The following example assumes that you are installing to a 64-bit Ubuntu Xenial system. Use dpkg to install the Debian package,as follows:

The installer will also try to build kernel modules suitable for the current running kernel. If the build process is not successful you will be shown a warning and the package will be left unconfigured. Look at /var/log/vbox-install.log to find out why the compilation failed. You may have to install the appropriate Linux kernel headers, see Section 2.3.2, 'The Oracle VM VirtualBox Kernel Modules'. After correcting any problems, run the following command:

This will start a second attempt to build the module.

If a suitable kernel module was found in the package or the module was successfully built, the installation script will attempt to load that module. If this fails, please see Linux Kernel Module Refuses to Load for further information.

Once Oracle VM VirtualBox has been successfully installed and configured, you can start it by clicking VirtualBox in your Start menu or from the command line. See Section 2.3.5, 'Starting Oracle VM VirtualBox on Linux'.

The alternative generic installer performs the following steps:

• Unpacks the application files to the target directory /opt/VirtualBox/, which cannot be changed.

• Builds and installs the Oracle VM VirtualBox kernel modules: vboxdrv, vboxnetflt, and vboxnetadp.

• Creates /sbin/rcvboxdrv, an init script to start the Oracle VM VirtualBox kernel module.

• Creates a new system group called vboxusers.

• Creates symbolic links in /usr/bin to a shell script /opt/VirtualBox/VBox which does some sanity checks and dispatches to the actual executables: VirtualBox, VBoxVRDP, VBoxHeadless and VBoxManage.

• Creates /etc/udev/rules.d/60-vboxdrv.rules, a description file for udev, if that is present, which makes the USB devices accessible to all users in the vboxusers group.

• Writes the installation directory to /etc/vbox/vbox.cfg.

The installer must be executed as root with either install or uninstall as the first parameter. For example:

Or if you do not have the sudo command available, run the following as root instead:

Add every user who needs to access USB devices from a VirtualBox guests to the group vboxusers. Either use the OS user management tools or run the following command as root:

The usermod command of some older Linux distributions does not support the -a option, which adds the user to the given group without affecting membership of other groups. In this case, find out the current group memberships with the groups command and add all these groups in a comma-separated list to the command line after the -G option. For example: usermod -G group1,group2,vboxusers username.

If you cannot use the shell script installer described in Section 2.3.3.2, 'Using the Alternative Generic Installer (VirtualBox.run)', you can perform a manual installation. Run the installer as follows:

This will unpack all the files needed for installation in the directory install under the current directory. The Oracle VM VirtualBox application files are contained in VirtualBox.tar.bz2 which you can unpack to any directory on your system. For example:

To run the same example as root, use the following commands:

The sources for Oracle VM VirtualBox's kernel module are provided in the src directory. To build the module, change to the directory and use the following command:

If everything builds correctly, run the following command to install the module to the appropriate module directory:

In case you do not have sudo, switch the user account to root and run the following command:

The Oracle VM VirtualBox kernel module needs a device node to operate. The above make command will tell you how to create the device node, depending on your Linux system. The procedure is slightly different for a classical Linux setup with a /dev directory, a system with the now deprecated devfs and a modern Linux system with udev.

On certain Linux distributions, you might experience difficulties building the module. You will have to analyze the error messages from the build system to diagnose the cause of the problems. In general, make sure that the correct Linux kernel sources are used for the build process.

Note that the /dev/vboxdrv kernel module device node must be owned by root:root and must be read/writable only for the user.

Next, you install the system initialization script for the kernel module and activate the initialization script using the right method for your distribution, as follows:

This example assumes you installed Oracle VM VirtualBox to the /opt/VirtualBox directory.

Create a configuration file for Oracle VM VirtualBox, as follows:

Create the following symbolic links:

Before updating or uninstalling Oracle VM VirtualBox, you must terminate any virtual machines which are currently running and exit the Oracle VM VirtualBox or VBoxSVC applications. To update Oracle VM VirtualBox, simply run the installer of the updated version. To uninstall Oracle VM VirtualBox, run the installer as follows:

As root, you can use the following command:

You can uninstall the .run package as follows:

To manually uninstall Oracle VM VirtualBox, perform the manual installation steps in reverse order.

The Debian packages will request some user feedback when installed for the first time. The debconf system is used to perform this task. To prevent any user interaction during installation, default values can be defined. A file vboxconf can contain the following debconf settings:

The first line enables compilation of the vboxdrv kernel module if no module was found for the current kernel. The second line enables the package to delete any old vboxdrv kernel modules compiled by previous installations.

These default settings can be applied prior to the installation of the Oracle VM VirtualBox Debian package, as follows:

In addition there are some common configuration options that can be set prior to the installation. See Section 2.3.3.7, 'Automatic Installation Options'.

The RPM format does not provide a configuration system comparable to the debconf system. See Section 2.3.3.7, 'Automatic Installation Options' for how to set some common installation options provided by Oracle VM VirtualBox.

To configure the installation process for .deb and .rpm packages, you can create a response file named /etc/default/virtualbox. The automatic generation of the udev rule can be prevented with the following setting:

The creation of the group vboxusers can be prevented as follows: Os 10 5 download free.

If the following line is specified, the package installer will not try to build the vboxdrv kernel module if no module fitting the current kernel was found.

The Linux installers create the system user group vboxusers during installation. Any system user who is going to use USB devices from Oracle VM VirtualBox guests must be a member of that group. A user can be made a member of the group vboxusers either by using the desktop user and group tools, or with the following command:

The easiest way to start an Oracle VM VirtualBox program is by running the program of your choice (VirtualBox, VBoxManage, or VBoxHeadless) from a terminal. These are symbolic links to VBox.sh that start the required program for you.

The following detailed instructions should only be of interest if you wish to execute Oracle VM VirtualBox without installing it first. You should start by compiling the vboxdrv kernel module and inserting it into the Linux kernel. Oracle VM VirtualBox consists of a service daemon, VBoxSVC, and several application programs. The daemon is automatically started if necessary. All Oracle VM VirtualBox applications will communicate with the daemon through UNIX local domain sockets. There can be multiple daemon instances under different user accounts and applications can only communicate with the daemon running under the user account as the application. The local domain socket resides in a subdirectory of your system's directory for temporary files called .vbox--ipc. In case of communication problems or server startup problems, you may try to remove this directory.

All Oracle VM VirtualBox applications (VirtualBox, VBoxManage, and VBoxHeadless) require the Oracle VM VirtualBox directory to be in the library path, as follows:

Copyright © 2004, 2020 Oracle and/or its affiliates. All rights reserved. Legal Notices

Oracle VirtualBox helps to run multiple OS at the same time on a single Computer Desktop or Laptop. VirtualBox is based on Virtualization technology, when you install a new Guest OS (Operating System) in the VirtualBox, then all the operating system files install inside a Virtual Disk Image (VDI) or Virtual Hard Drive (VHD), so it doesn't mess another operating system files into main OS. Hence, VirtualBox is one best solution to install & run single or multiple Guest Operating Systems on a single PC.

Before installing any Guest OS including Windows, Linux, Solaris, BSD, IBM (OS2), Mac OS X and many others in the VirtualBox Virtual Machine, you need to understand some its basic installation instructions, so when you follow below steps, you won't face any trouble after finalizing full setup.

VirtualBox Guest OS Installation Instructions:

VirtualBox offers two Guest OS setup mode (1) Expert Mode(2) Guided Mode. By default, when you start creating a Virtual Hard Disk, then it begins with Expert Mode, if you can't understand the Expert mode then Guided mode will be easy to setup, but we will continue with Expert Mode because we have much better control on this than Guided Mode. So follow all below step by step points to install Guest OS in VirtualBox.

1) First Start the Oracle VM VirtualBox Manager using desktop Icon or from Start Menu. When Oracle VM VirtualBox Manager screen appears, click on the new icon from the top left screen. Now Create Virtual Machine dialog box will appear where you can select following things:

Name and operating system

• Name: Give an Operating System Name, you can choose any name that you want.
• Type: You can select any Guest Operating System from Microsoft Windows. Linux, Solaris, BSD, IBM (OS2), Mac OS X and others.
• Version: In this dropdown list, you will see all supported OS series version, which is related to Company, suppose you have selected Microsoft Windows from the Type dropdown list menu, then from the Version list menu you can select the Microsoft Windows related release version such as Windows XP, Vista, 7, 8.1, 10, etc.

Memory size:

When you chose any OS version then VirtualBox will automatically select the necessary value of the Memory, or if you want to increase or decrease the allotted memory size, it is also possible using memory size slider. If you don't know how much memory is needed by the selected OS? then you can read OS developers site to check the minimum requirement for running the OS smoothly.

Hard disk

• Do not add a virtual hard disk: Select the radio button if you don't want to add a virtual hard disk.
• Create a virtual hard disk now: You can create a new Virtual Hard Disk, best option if you're installing a new Guest OS.
• Use an existing virtual hard disk file: If you're reinstalling Virtual and want to add previously created VHD or VDI image then you can choose this option.

After selecting required settings, click on the Create button.

2) Next, you'll see Create Virtual Hard Disk dialog box. Here you can settings-up Virtual Hard Disk:

File location:

Here you can enter a different Virtual Hard Disk storage location. Suppose your C drive is full or it has low storage problem then you can save the VHD file on a different drive. To save the VHD on a custom place, you can enter the full path of the location. Alternatively, you can use Choose a location for new hard disk file… icon.

File Size:

You can use File size slider to increase or decrease the VHD size. It is only useful if you select Fixed size radio button from the Storage on physical hard disk section. If you choose the dynamically allocated option, then the hard drive size will automatically decrease and increase continuously.

Hard disk file type:

Using this option you can create & save the VirtualBox Disk Image file to different format. Such as VHD (Virtual Hard Disk), VMDK (Virtual Disk Machine Disk), HDD (Parallels Hard Disk) QCOW (QEMU Copy-On-Write), QED (QEMU enhanced disk). So later these disks can be used with other Virtual Machine software eg: VMWARE, Parallel Virtual Machine, etc.

Storage on physical hard disk:

Dynamically allocated: Select this if you want that VirtualBox automatically increases or decrease the size of the Virtual Drive size. It is most popular and widely used option, and we also recommend you to select this option because when you install new software into the Guest OS then Drive size will be increased, so Virtualbox will adjust the virtual drive size automatically as OS required.

Fixed Size: We recommend this only when you will not install the unwanted software, suppose you want to use the installed Guest OS only for specific software and once you installed it and will continue use then it won't needed any extra space on the drive.

• Split into files of less than 2GB: This option will help to split Virtual Hard Drive into 2GB part each. It is the best option if you're using the FAT32 file system on the physical drive.

Best Linux For Virtualbox

Once you select all the correct options, you can continue to setup by clicking on the Create button.

3) Now Virtual Hard Drive has been added to the Oracle VirtualBox Manager. To continue setup click on the Virtual Drive name and click on the Start icon.

4) Now, Windows Setup will be started and you'll get Select start-up disk dialog box. Here, you'll need to select the drive such as DVD or USB Drive or if you only have ISO image file that contains the Operating System files then it can be also manually selected. For ISO image selection you can browse the folder and files using folder icon.

Oracle Vm Virtualbox Download

5) Next, you can select the ISO image file via file explorer and click on the Open Button.

6) Once you made the selection of the drive or ISO image, you can click on the Start button.

Since distributing driver modules separately from the kernel is not something which Linux supports well, the Oracle VM VirtualBox install process creates the modules on the system where they will be used. This means that you may need to install some software packages from the distribution which are needed for the build process. Required packages may include the following:

• GNU compiler (GCC)

• GNU Make (make)

• Kernel header files

Also ensure that all system updates have been installed and that your system is running the most up-to-date kernel for the distribution.

The running kernel and the kernel header files must be updated to matching versions.

The following list includes some details of the required files for some common distributions. Start by finding the version name of your kernel, using the command uname -r in a terminal. The list assumes that you have not changed too much from the original installation, in particular that you have not installed a different kernel type.

• With Debian and Ubuntu-based distributions, you must install the correct version of the linux-headers, usually whichever of linux-headers-generic, linux-headers-amd64, linux-headers-i686 or linux-headers-i686-pae best matches the kernel version name. Also, the linux-kbuild package if it exists. Basic Ubuntu releases should have the correct packages installed by default.

• On Fedora, Red Hat, Oracle Linux and many other RPM-based systems, the kernel version sometimes has a code of letters or a word close to the end of the version name. For example 'uek' for the Oracle Unbreakable Enterprise Kernel or 'default' or 'desktop' for the standard kernels. In this case, the package name is kernel-uek-devel or equivalent. If there is no such code, it is usually kernel-devel.

• On some SUSE and openSUSE Linux versions, you may need to install the kernel-source and kernel-syms packages.

If you suspect that something has gone wrong with module installation, check that your system is set up as described above and try running the following command, as root:

If you are running on a system using UEFI (Unified Extensible Firmware Interface) Secure Boot, you may need to sign the following kernel modules before you can load them:

• vboxdrv

• vboxnetadp

• vboxnetflt

• vboxpci

See your system documentation for details of the kernel module signing process.

Oracle VM VirtualBox is available in a number of package formats native to various common Linux distributions. See Section 1.4, 'Supported Host Operating Systems'. In addition, there is an alternative generic installer (.run) which you can use on supported Linux distributions.

Download the appropriate package for your distribution. The following example assumes that you are installing to a 64-bit Ubuntu Xenial system. Use dpkg to install the Debian package,as follows:

The installer will also try to build kernel modules suitable for the current running kernel. If the build process is not successful you will be shown a warning and the package will be left unconfigured. Look at /var/log/vbox-install.log to find out why the compilation failed. You may have to install the appropriate Linux kernel headers, see Section 2.3.2, 'The Oracle VM VirtualBox Kernel Modules'. After correcting any problems, run the following command:

This will start a second attempt to build the module.

If a suitable kernel module was found in the package or the module was successfully built, the installation script will attempt to load that module. If this fails, please see Linux Kernel Module Refuses to Load for further information.

Once Oracle VM VirtualBox has been successfully installed and configured, you can start it by clicking VirtualBox in your Start menu or from the command line. See Section 2.3.5, 'Starting Oracle VM VirtualBox on Linux'.

The alternative generic installer performs the following steps:

• Unpacks the application files to the target directory /opt/VirtualBox/, which cannot be changed.

• Builds and installs the Oracle VM VirtualBox kernel modules: vboxdrv, vboxnetflt, and vboxnetadp.

• Creates /sbin/rcvboxdrv, an init script to start the Oracle VM VirtualBox kernel module.

• Creates a new system group called vboxusers.

• Creates symbolic links in /usr/bin to a shell script /opt/VirtualBox/VBox which does some sanity checks and dispatches to the actual executables: VirtualBox, VBoxVRDP, VBoxHeadless and VBoxManage.

• Creates /etc/udev/rules.d/60-vboxdrv.rules, a description file for udev, if that is present, which makes the USB devices accessible to all users in the vboxusers group.

• Writes the installation directory to /etc/vbox/vbox.cfg.

The installer must be executed as root with either install or uninstall as the first parameter. For example:

Or if you do not have the sudo command available, run the following as root instead:

Add every user who needs to access USB devices from a VirtualBox guests to the group vboxusers. Either use the OS user management tools or run the following command as root:

The usermod command of some older Linux distributions does not support the -a option, which adds the user to the given group without affecting membership of other groups. In this case, find out the current group memberships with the groups command and add all these groups in a comma-separated list to the command line after the -G option. For example: usermod -G group1,group2,vboxusers username.

If you cannot use the shell script installer described in Section 2.3.3.2, 'Using the Alternative Generic Installer (VirtualBox.run)', you can perform a manual installation. Run the installer as follows:

This will unpack all the files needed for installation in the directory install under the current directory. The Oracle VM VirtualBox application files are contained in VirtualBox.tar.bz2 which you can unpack to any directory on your system. For example:

To run the same example as root, use the following commands:

The sources for Oracle VM VirtualBox's kernel module are provided in the src directory. To build the module, change to the directory and use the following command:

If everything builds correctly, run the following command to install the module to the appropriate module directory:

In case you do not have sudo, switch the user account to root and run the following command:

The Oracle VM VirtualBox kernel module needs a device node to operate. The above make command will tell you how to create the device node, depending on your Linux system. The procedure is slightly different for a classical Linux setup with a /dev directory, a system with the now deprecated devfs and a modern Linux system with udev.

On certain Linux distributions, you might experience difficulties building the module. You will have to analyze the error messages from the build system to diagnose the cause of the problems. In general, make sure that the correct Linux kernel sources are used for the build process.

Note that the /dev/vboxdrv kernel module device node must be owned by root:root and must be read/writable only for the user.

Next, you install the system initialization script for the kernel module and activate the initialization script using the right method for your distribution, as follows:

This example assumes you installed Oracle VM VirtualBox to the /opt/VirtualBox directory.

Create a configuration file for Oracle VM VirtualBox, as follows:

Create the following symbolic links:

Before updating or uninstalling Oracle VM VirtualBox, you must terminate any virtual machines which are currently running and exit the Oracle VM VirtualBox or VBoxSVC applications. To update Oracle VM VirtualBox, simply run the installer of the updated version. To uninstall Oracle VM VirtualBox, run the installer as follows:

As root, you can use the following command:

You can uninstall the .run package as follows:

To manually uninstall Oracle VM VirtualBox, perform the manual installation steps in reverse order.

The Debian packages will request some user feedback when installed for the first time. The debconf system is used to perform this task. To prevent any user interaction during installation, default values can be defined. A file vboxconf can contain the following debconf settings:

The first line enables compilation of the vboxdrv kernel module if no module was found for the current kernel. The second line enables the package to delete any old vboxdrv kernel modules compiled by previous installations.

These default settings can be applied prior to the installation of the Oracle VM VirtualBox Debian package, as follows:

In addition there are some common configuration options that can be set prior to the installation. See Section 2.3.3.7, 'Automatic Installation Options'.

The RPM format does not provide a configuration system comparable to the debconf system. See Section 2.3.3.7, 'Automatic Installation Options' for how to set some common installation options provided by Oracle VM VirtualBox.

To configure the installation process for .deb and .rpm packages, you can create a response file named /etc/default/virtualbox. The automatic generation of the udev rule can be prevented with the following setting:

The creation of the group vboxusers can be prevented as follows: Os 10 5 download free.

If the following line is specified, the package installer will not try to build the vboxdrv kernel module if no module fitting the current kernel was found.

The Linux installers create the system user group vboxusers during installation. Any system user who is going to use USB devices from Oracle VM VirtualBox guests must be a member of that group. A user can be made a member of the group vboxusers either by using the desktop user and group tools, or with the following command:

The easiest way to start an Oracle VM VirtualBox program is by running the program of your choice (VirtualBox, VBoxManage, or VBoxHeadless) from a terminal. These are symbolic links to VBox.sh that start the required program for you.

The following detailed instructions should only be of interest if you wish to execute Oracle VM VirtualBox without installing it first. You should start by compiling the vboxdrv kernel module and inserting it into the Linux kernel. Oracle VM VirtualBox consists of a service daemon, VBoxSVC, and several application programs. The daemon is automatically started if necessary. All Oracle VM VirtualBox applications will communicate with the daemon through UNIX local domain sockets. There can be multiple daemon instances under different user accounts and applications can only communicate with the daemon running under the user account as the application. The local domain socket resides in a subdirectory of your system's directory for temporary files called .vbox--ipc. In case of communication problems or server startup problems, you may try to remove this directory.

All Oracle VM VirtualBox applications (VirtualBox, VBoxManage, and VBoxHeadless) require the Oracle VM VirtualBox directory to be in the library path, as follows:

Copyright © 2004, 2020 Oracle and/or its affiliates. All rights reserved. Legal Notices

Oracle VirtualBox helps to run multiple OS at the same time on a single Computer Desktop or Laptop. VirtualBox is based on Virtualization technology, when you install a new Guest OS (Operating System) in the VirtualBox, then all the operating system files install inside a Virtual Disk Image (VDI) or Virtual Hard Drive (VHD), so it doesn't mess another operating system files into main OS. Hence, VirtualBox is one best solution to install & run single or multiple Guest Operating Systems on a single PC.

Before installing any Guest OS including Windows, Linux, Solaris, BSD, IBM (OS2), Mac OS X and many others in the VirtualBox Virtual Machine, you need to understand some its basic installation instructions, so when you follow below steps, you won't face any trouble after finalizing full setup.

VirtualBox Guest OS Installation Instructions:

VirtualBox offers two Guest OS setup mode (1) Expert Mode(2) Guided Mode. By default, when you start creating a Virtual Hard Disk, then it begins with Expert Mode, if you can't understand the Expert mode then Guided mode will be easy to setup, but we will continue with Expert Mode because we have much better control on this than Guided Mode. So follow all below step by step points to install Guest OS in VirtualBox.

1) First Start the Oracle VM VirtualBox Manager using desktop Icon or from Start Menu. When Oracle VM VirtualBox Manager screen appears, click on the new icon from the top left screen. Now Create Virtual Machine dialog box will appear where you can select following things:

Name and operating system

• Name: Give an Operating System Name, you can choose any name that you want.
• Type: You can select any Guest Operating System from Microsoft Windows. Linux, Solaris, BSD, IBM (OS2), Mac OS X and others.
• Version: In this dropdown list, you will see all supported OS series version, which is related to Company, suppose you have selected Microsoft Windows from the Type dropdown list menu, then from the Version list menu you can select the Microsoft Windows related release version such as Windows XP, Vista, 7, 8.1, 10, etc.

Memory size:

When you chose any OS version then VirtualBox will automatically select the necessary value of the Memory, or if you want to increase or decrease the allotted memory size, it is also possible using memory size slider. If you don't know how much memory is needed by the selected OS? then you can read OS developers site to check the minimum requirement for running the OS smoothly.

Hard disk

• Do not add a virtual hard disk: Select the radio button if you don't want to add a virtual hard disk.
• Create a virtual hard disk now: You can create a new Virtual Hard Disk, best option if you're installing a new Guest OS.
• Use an existing virtual hard disk file: If you're reinstalling Virtual and want to add previously created VHD or VDI image then you can choose this option.

After selecting required settings, click on the Create button.

2) Next, you'll see Create Virtual Hard Disk dialog box. Here you can settings-up Virtual Hard Disk:

File location:

Here you can enter a different Virtual Hard Disk storage location. Suppose your C drive is full or it has low storage problem then you can save the VHD file on a different drive. To save the VHD on a custom place, you can enter the full path of the location. Alternatively, you can use Choose a location for new hard disk file… icon.

File Size:

You can use File size slider to increase or decrease the VHD size. It is only useful if you select Fixed size radio button from the Storage on physical hard disk section. If you choose the dynamically allocated option, then the hard drive size will automatically decrease and increase continuously.

Hard disk file type:

Using this option you can create & save the VirtualBox Disk Image file to different format. Such as VHD (Virtual Hard Disk), VMDK (Virtual Disk Machine Disk), HDD (Parallels Hard Disk) QCOW (QEMU Copy-On-Write), QED (QEMU enhanced disk). So later these disks can be used with other Virtual Machine software eg: VMWARE, Parallel Virtual Machine, etc.

Storage on physical hard disk:

Dynamically allocated: Select this if you want that VirtualBox automatically increases or decrease the size of the Virtual Drive size. It is most popular and widely used option, and we also recommend you to select this option because when you install new software into the Guest OS then Drive size will be increased, so Virtualbox will adjust the virtual drive size automatically as OS required.

Fixed Size: We recommend this only when you will not install the unwanted software, suppose you want to use the installed Guest OS only for specific software and once you installed it and will continue use then it won't needed any extra space on the drive.

• Split into files of less than 2GB: This option will help to split Virtual Hard Drive into 2GB part each. It is the best option if you're using the FAT32 file system on the physical drive.

Best Linux For Virtualbox

Once you select all the correct options, you can continue to setup by clicking on the Create button.

3) Now Virtual Hard Drive has been added to the Oracle VirtualBox Manager. To continue setup click on the Virtual Drive name and click on the Start icon.

4) Now, Windows Setup will be started and you'll get Select start-up disk dialog box. Here, you'll need to select the drive such as DVD or USB Drive or if you only have ISO image file that contains the Operating System files then it can be also manually selected. For ISO image selection you can browse the folder and files using folder icon.

Oracle Vm Virtualbox Download

5) Next, you can select the ISO image file via file explorer and click on the Open Button.

6) Once you made the selection of the drive or ISO image, you can click on the Start button.

7) The OS setup has been started and Now you can easily follow all the steps ahead as you install OS normally on the physical machine.

That's it, you've understood all the steps and can install any OS in VirtualBox as a Guest Operating System. However, if you still have any confusion regarding the setup, please leave a comment reply, we will try to give your queries answer as soon as possible.

Download Linux Os For Oracle Virtualbox Free

You May Also Like: