When most people run VirtualBox (vbox for short), they install the package, double click on the virtual box icon, and off they go. That is fine when you are running it off your desktop or in a server that has a gui (a Windows server does come to mind, being immediately followed by its OSX brethen). But, what if you are remotely connecting to a server through ssh or just do not want to run the gui? Or, what if you want to have vbox start/stop the vms automagically (say, during a reboot)?
Well, you can do that: like VMWare, KVM, and Xen, vbox allows you to do a lot of interesting things through the command line. Since I wrote Virtual Box in the title, I better focus on vbox. In this episode, how about if we create a little test vm from scratch?
We will use an 64bit ubuntu server as example, assuming we already downloaded the iso for it (I also like to convert install CDs/DVDs to ISOs so I can do it all remotely). We will create the VM as user root instead of your normal user.
- First step is to create a directory to put the VMs. Because I came from solaris, I
tend to put stuff in /export; ubuntu likes to put it in /srv. It is your server, you do whatever you want. Anywhoo,
sudo mkdir -p /export/vms
NOTE: I also like to have /export in a different partition. Well, I do like to partition the hard drive both for security and to avoid the important partitions running out of space. LVM is great here too.
- Define the vm
sudo VBoxManage createvm --name "testbox" --basefolder /export/vms --register
Output should look like this:
Virtual machine 'testbox' is created and registered. UUID: 260ac334-d914-47af-842d-378275130c0f Settings file: '/export/vms/testbox/testbox.vbox'
Note the vm has its own UUID; this can be used to refer to it down the line, but I rarely need it. Just be ware it is there. Now, if you go to /export/vms, you will see a new directory called testbox
- Let's configure testbox:
sudo VBoxManage modifyvm "testbox" --ostype "Ubuntu_64" --memory "256" --hwvirtex on --nestedpaging on --cpus 1
I am only giving it 256MB because I do not plan on running apache or
other memory-intensive application in it. Also, note I am only giving it 1 CPU but am telling it to use the hardware virtualization provided by my CPU; do check whether yours is enabled or not.
- We need to define its network card. I will set it to be an intel gigabit (since it is nicely supported by all the Linux distros I have met) and set it to bridged mode, so it will be visible in the same network as the vm host:
sudo VBoxManage modifyvm "testbox" --nic1 bridged --nictype1 82543GC --bridgeadapter1 eth0
- Now we need a hard drive. I think a 10GB hard drive will do; this
is just a test. I will use the .vdi format so it will expand itself up
to 10GB as needed. Note we can always add more drives later. Or move
stuff around. Or even resize.
sudo VBoxManage createhd --filename "/export/vms/testbox/drive1.vdi" --size 10000 --format VDI
We will attach it to the SATA chain.
sudo VBoxManage modifyvm "testbox" --sata on sudo VBoxManage modifyvm "testbox" --sataportcount 4 sudo VBoxManage storageattach "testbox" \ --storagectl SATA --port 1 --device 0 \ --medium "/export/vms/testbox/drive1.vdi" --type hdd
- Remember the installation disk we downloaded as .iso? It is time to feed it to the vm. Just to be different, let's put it in the IDE chain. I am guessing the ISO is in, say, /export/ISOs.
sudo VBoxManage storagectl "testbox" --name IDE --add ide --controller PIIX4 sudo VBoxManage storageattach "testbox" \ --storagectl IDE --port 1 --device 0 \ --medium "/export/ISO/ubuntu-12.04-desktop-amd64.iso" \ --type dvddrive
- And now to define the vrdp/vrde port (say, 5050) so we can do a
remote install. This will not work right of the boxl you must first download and install the VirtualBox Extension Pack, which is conveniently found at https://www.virtualbox.org/wiki/Downloads. Once that is installed, you can then do
sudo VBoxManage modifyvm "testbox" --vrdeport 5050 --vrde on \ --vrdeauthtype external
And that should be it. Now we need to start the VM. Something like
sudo VBoxHeadless --startvm "testbox" &
should do the trick. Now, we can and should have a script to start and stop the vm and any vms we have running in the machine (say, when vm host/server is shut down/restarted), but we can talk about that later.
You probably noticed you would be happier by writing a script do to all the steps we did above; we shall talk about that in another episode.