Tutorials, Guides, Tips, and Tricks from Everyday Experiences

Here's everything we could find about: "VirtualBox"

This is a step by step tutorial on how to get VirtualBox 4.0 up and running on Fedora 15 (Lovelock). Specifically, this guide was written using the VirtualBox 4.0 (32-bit) version (Package: kernel-devel.i686 0:2.6.38.8-32.fc15). It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Open a terminal window and let’s get to it…[Read more →]

This is a step by step tutorial on how to get VirtualBox 3.2 up and running on Fedora 14. Specifically, this guide was written using the VirtualBox 3.2.10 (32-bit) version. It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Right, open a terminal window and let’s get to it…[Read more →]

This is a step by step tutorial on how to get VirtualBox 3.2 up and running on Fedora 13. Specifically, this guide was written using the VirtualBox 3.2.0 (32-bit) version. It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Right, open a terminal window and let’s get to it…[Read more →]

I hadn’t realized this before, but you can shrink a dynamic VirtualBox disk image. This is incredibly helpful if you’ve uninstalled programs or freed up a bunch of space and you want the .vdi image size to reflect that. Otherwise, the dynamic disk image will stay the same size it was before. The process is simple, but can be a bit involved so I’ll just touch on the basics and then refer you to a few guides that were really helpful when I did this for my Ubuntu 9.10 VirtualBox image. These guides can be applied to other guest images as well.

This is a step by step tutorial on how to get VirtualBox 3 up and running on Fedora 12. Specifically, this guide was written using the VirtualBox 3.0.8 version and an i386 CPU (32-bit). It can be adapted to upcoming versions and different CPUs (64-bit). The folks at VirtualBox have made it easy to install for Fedora users and I’m going to show you how in a few easy steps. Right, open a terminal window and let’s get to it…[Read more →]

Note: I have been unable to verify these steps. They should work just fine, but I’m a little concerned about the USB support fix. You may or may not want to try it at this point. I have it here just as a reference for now.

This is a tutorial on how to get VirtualBox up and running on Fedora 11. Also, this tutorial is for the 32-Bit version of VirtualBox, so you’ll have to customize a little more to get the 64-bit version running. Everything in the “code” sections should be copy/pasted/typed into the terminal. Right, let’s get to it:

PreStep.) Open the terminal and get into super user mode:su -

1.) Get the latest VirtualBox package (as of now, 2.2.4) from the VirtualBox website for Fedora 11 and install it. The following command should download and install the application:wget http://download.virtualbox.org/virtualbox/2.2.4/VirtualBox-2.2.4_47978_fedora11-1.i586.rpm && rpm -ivh VirtualBox-2.2.4_47978_fedora11-1.i586.rpm

2.) Get the kernel-devel and other needed packages:yum install make automake autoconf gcc kernel-devel dkms

Highlight your virtual machine and click on the “Settings” button. Click on the “Sound” category, and then check the “Enable Sound” option. In the drop-down box, select “PulseAudio”. You should now have sound.

That’s it! If you find yourself with problems, feel free to comment below or ask for assistance on the fedora forum thread that I have created located here.

This is a tutorial on how to get VirtualBox up and running on Fedora 10. Also, this tutorial is for the 32-Bit version of VirtualBox, so you’ll have to customize a little more to get the 64-bit version running. Everything in the “code” sections should be copy/pasted/typed into the terminal. Right, let’s get to it:

PreStep.) Open the terminal and get into super user mode:

su -

1.) Get the latest VirtualBox package (as of now, 2.0.6) from the VirtualBox website for Fedora 9 and install it (generally, after a few months, the Fedora 10 link will be available).

Highlight your virtual machine and click on the “Settings” button. Click on the “Sound” category, and then check the “Enable Sound” option. In the drop-down box, select “PulseAudio”. You should now have sound.

That’s it! If you find yourself with problems, feel free to comment below or ask for assistance on the fedora forum thread that I have created located here.

Update on 27 July 2011:

The VM cloning tool is now built into the GUI as of VirtualBox 4.1. See the changelog:

VirtualBox 4.1.0 (released 2011-07-19)
This version is a major update. The following major new features were added:
Support for cloning of VMs (bug #5853, see the manual for more information): full clones can be created through the GUI and VBoxManage, linked clones only through VBoxManage
GUI: enhanced wizard for creating new virtual disks
GUI: new wizard for copying virtual disks
...

Original Post:

First of all, these are the instructions for a VirtualBox installation on a Linux host. It may or may not be the same directory structure/commands for Windows or Mac OS X hosts.

Most people don’t realize that making a backup of a VirtualBox Machine (.vdi) is more complex than just copy/paste. If you do that, you’ll soon realize (when it’s too late) that it doesn’t work! This is the proper way to backup your VirtualBox Machine:

NOTE: Although I’m not specifically sure, sometime after Version 2 of this software, the clonedvi command has been replaced with clonehd (see page 108 of the VirtualBox Manual), however, clonedvi will still work as they kept the backwards compatibility.

Then, wait for it to complete. It may take a while depending on the size of your .vdi file (or how much space you allocated towards your virtual machine).
What this actually does is create a new UUID (Universal Unique Identifier) for the cloned VM. This way, you won’t end up with a message similar to this:

A hard disk with UUID {4d749826-6a3f-43ff-90af-42618783bd3a} or with the
same properties (’/home/martin/.VirtualBox/VDI/test.vdi’) is already
registered.