VBoxHeadless - Running Virtual Machines With VirtualBox 4.0 On A Headless Fedora 14 Server
Author: Falko Timme
Follow me on Twitter
This guide explains how you can run virtual machines with VirtualBox 4.0 on a headless Fedora 14 server. Normally you use the VirtualBox GUI to manage your virtual machines, but a server does not have a desktop environment. Fortunately, VirtualBox comes with a tool called VBoxHeadless that allows you to connect to the virtual machines over a remote desktop connection, so there's no need for the VirtualBox GUI.
I do not issue any guarantee that this will work for you!
1 Preliminary Note
I have tested this on a Fedora 14 server (host system) with the IP address 192.168.0.100 where I'm logged in as a normal user (user name admin in this example) instead of as root.
If you only have a root account, but no normal user account, create one as follows (user admin, group admin)...
# groupadd admin
# useradd -d /home/admin -m -g admin -s /bin/bash admin
... create a password for the new user...
# passwd admin
... and log in as that user.
2 Installing VirtualBox
To install VirtualBox 4.0 on our Fedora 14 server, we need root privileges, therefore we run
Then we install the dependencies for VirtualBox 4.0 as follows:
# yum groupinstall 'Development Tools'
# yum groupinstall 'Development Libraries'
# yum install SDL kernel-devel kernel-headers dkms
Next we pick the right VirtualBox package from http://www.virtualbox.org/wiki/Linux_Downloads; pick the i386 or AMD64 package (depending on your architecture) for Fedora 14 ("Laughlin") (you can find out your architecture by running
# uname -m
The output on my test system is
which means I must pick the AMD64 package.
... and download it as follows:
# cd /tmp
# wget http://download.virtualbox.org/virtualbox/4.0.0/VirtualBox-4.0-4.0.0_69151_fedora14-1.x86_64.rpm
Afterwards, we install VirtualBox 4.0 as follows:
# yum --nogpgcheck install VirtualBox-4.0-4.0.0_69151_fedora14-1.x86_64.rpm
Starting with version 4.0, VirtualBox has introduced so called "extension packs" and has outsourced some functionality like remote desktop connection support (VRDP) that was part of VirtualBox packages before version 4.0 into these extension packs. Because we need remote desktop connections to control our virtual machines, we need to install the appropriate extension pack now. Go to http://www.virtualbox.org/wiki/Downloads, and you will find a link to the following extension pack:
VirtualBox 4.0 Oracle VM VirtualBox Extension Pack
Support for USB 2.0 devices, VirtualBox RDP and PXE boot for Intel cards
Download and install the extension pack as follows:
# cd /tmp
# wget http://download.virtualbox.org/virtualbox/4.0.0/Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack
# VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.0.0-69151.vbox-extpack
(Make sure you grab the latest version from the VirtualBox web site.)
Now we must add the user that will run VirtualBox (admin in this example) to the vboxusers group:
# /usr/sbin/usermod -G vboxusers admin
VirtualBox is now installed and ready to be used.
to leave the root account and become a normal user (admin) again.
3 Using VirtualBox On The Command Line
3.1 Creating A VM
To create a VM on the command line, we can use the VBoxManage command. See
$ VBoxManage --help
for a list of available switches and (highly recommended!) take a look at http://www.virtualbox.org/manual/ch08.html.
I will now create an Ubuntu 10.10 Server VM with 256MB memory and a 10GB hard drive from the Ubuntu 10.10 Server iso image (which I have stored in /home/ubuntu-10.10-server-amd64.iso):
$ VBoxManage createvm --name "Ubuntu 10.10 Server" --register
$ VBoxManage modifyvm "Ubuntu 10.10 Server" --memory 256 --acpi on --boot1 dvd --nic1 bridged --bridgeadapter1 eth0
$ VBoxManage createhd --filename Ubuntu_10_10_Server.vdi --size 10000
$ VBoxManage storagectl "Ubuntu 10.10 Server" --name "IDE Controller" --add ide
$ VBoxManage storageattach "Ubuntu 10.10 Server" --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium Ubuntu_10_10_Server.vdi
$ VBoxManage storageattach "Ubuntu 10.10 Server" --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium /home/ubuntu-10.10-server-amd64.iso
3.2 Importing An Existing VM
Let's assume you have a VM called examplevm that you want to reuse on this host. On the old host, you should have a directory Machines/examplevm in the VirtualBox directory; Machines/examplevm should contain the examplevm.xml file. Copy the examplevm directory (including the examplevm.xml file) to your new Machines directory (if your user name is admin, this is /home/admin/.VirtualBox/Machines - the result should be /home/admin/.VirtualBox/Machines/examplevm/examplevm.xml).
In addition to that copy the examplevm.vdi file from the old VDI directory to the new one (e.g. /home/admin/.VirtualBox/VDI/examplevm.vdi).
Afterwards, you must register the imported VM:
$ VBoxManage registervm Machines/examplevm/examplevm.xml
3.3 Starting A VM With VBoxHeadless
Regardless of if you create a new VM or import and old one, you can start it with the command:
$ VBoxHeadless --startvm "Ubuntu 10.10 Server"
(Replace Ubuntu 10.10 Server with the name of your VM.)
VBoxHeadless will start the VM and a VRDP (VirtualBox Remote Desktop Protocol) server which allows you to see the VM's output remotely on another machine.
To stop a VM, run
$ VBoxManage controlvm "Ubuntu 10.10 Server" poweroff
To pause a VM, run
$ VBoxManage controlvm "Ubuntu 10.10 Server" pause
To reset a VM, run
$ VBoxManage controlvm "Ubuntu 10.10 Server" reset
To learn more about VBoxHeadless, take a look at
$ VBoxHeadless --help