Posted by: Rick Vanover
Rick Vanover, Sun xVM, VirtualBox, Virtualization
The configuration for virtual machine (VM) tasks that involve booting from anything other than the virtual disk can be inconvenient. Sun xVM VirtualBox offers a functionality that allows the boot order to be configured outside of the VM. For VirtualBox guests, the boot order can be configured in the VM’s advanced options. The figure below shows a VM’s configured boot order properties.
The limitation with this configuration is that the settings cannot be accessed through the VirtualBox interface while the VM is running, which makes advanced configuration a little difficult. Further, if the machine is in a saved state but not running, it cannot be configured. The vboxmanage command can perform this same configuration but it still requires offline access to the VM. VMware products have a BIOS for the VM, making configuration similar to that of a physical machine for boot order. With VirtualBox, there is not an accessible BIOS interface for the VM. During the boot process, however, there is a default option to access a boot menu by pressing F12. This functionality is shown below.
By VirtualBox not having a VM BIOS in a conventional sense, all relevant configuration is accessible from the interface. The four standard boot classes of hard disk, network, floppy or optical drive can be configured in the interface as shown above or with the earlier mentioned vboxmanage command. The following command will configure the boot order of the Solaris-Test VM:
vboxmanage modifyvm Solaris-Test -boot1 disk
I’ve mentioned the vboxmanage command before for amazing configuration options from the command line. In the case of boot configurations, virtual media (.ISO and .FLP files) can be configured as well.
Version 2.0.2 of VirtualBox was released on September 12, 2008. More information on Sun xVM VirtualBox can be found in the online user manual at the VirtualBox website.