VirtualBox is a powerful virtualization product for enterprise as well as home use. Not only is Virtual Box an extremely feature rich, high performance product for enterprise customers; It is also the only professional solution that is freely available as Open Source Software.
VirtualBox 3.0 is capable of creating and running multi-processor virtual machines that can handle heavyweight server-class workloads, and also delivers enhanced graphics support for desktop-class workloads, reinforcing VirtualBox’s position as one of the world’s most popular virtualization platforms. Many multi-threaded server-based workloads, such as database and Web applications, can benefit from Symmetric Multiple Processing (SMP) systems, which contain multiple CPUs. VirtualBox 3.0 can now support virtual SMP systems with up to 32 virtual CPUs (vCPUs) in a single virtual machine. With this major enhancement, VirtualBox software can be used to run not only desktop workloads on client or server systems, but also demanding server workloads.
New server features of VirtualBox 3.0 software include:
- Up to 32 vCPUs per guest to accommodate heavyweight data-processing workloads.
- Hypervisor enhancements for SMP to enable optimum performance.
- Updated API platform designed to be the basis of the community-driven VirtualBox Web Console project, which is coming soon to allow IT administrators to manage their datacenters from a Web console. This project is based on the popular Python language.
New desktop features of VirtualBox 3.0 software include:
- Microsoft Direct3D support for Windows guests, which enables graphically intensive Windows applications, like computer modeling, 3D design and games software, to run in a virtual environment.
- Support for version 2.0 of the Open Graphics Library (OpenGL) standard. As a result, high-performance Windows, Linux, Solaris(TM), and OpenSolaris(TM) graphical applications, which typically use graphical hardware acceleration, are able to run applications like Google Earth and CAM-based software on VirtualBox software.
- Support for a wider range of USB devices, including storage devices, iPods and phones.
Creating an Ubuntu Virtual Machine using VirtualBox 3.0
After Installing the VirtualBox software, Invoke the shortcut to launch the application. Click on New buttom which is present under the file menu. This will give you options to install various Operating Systems. (as shown below)
Step 1: In this example, we will choose Linux and Ubuntu, Click Next
Step 2: In this below dialog, we will select the amount of base memory to be allocated to the Ubuntu VM. You can use the slider or enter the number in the text box provided. I will choose 512 MB, Click Next
Step 3: IF you already have a disk image, you can load that. Else, you can create a new hard disk using the New Button. I will select the New button here,
Step 4: You now have an option to create a Virtual hardrive with Fixed size or dynamic size storage. Using a Dynamic Size storage is always a better practice.Click Next
Step 5: You can do the lower bound of the hard-drive space allocation here. (By default, the Virtual disk will be saved in C:\Users\Vj\.VirtualBox\HardDisks\Ubunto.vdi ) – Click Next
Step 6:That completes the Configuration settings for the newly built Virtual Machine. Click Finish.
Step 7: On completion, you will get this dialog. However, you will need an OS CD/DVD to boot the installation. Click on Settings button, which is present next to the New button. Select CD/DVD ROM, and you can choose the physical CD-ROM drive or an iso file.
Step 8: You can add an Iso image, using the add button in the Virtual Media Manager dialog
Step 9: Now you are all set to start the Virtual Machine, and install Ubuntu OS on it. Click the Start Button, which is present next to the Settings. (see below image)
Step 10: Follow the OS setup Instructions, and Booom, your Virtual Machine is ready to use.
Step 11: You can do all the addition configurations like sharing folders, create multiple snapshots, mounting drives etc using simple menu options. See below
Installing the Guest Additions is always a better practice. This will make the virtual machine, more responsive.
Call to Actions: