Page 1: User Manual
Sun VirtualBox User Manual Version 3.0.0 c 2004-2009 Sun Microsystems, Inc. http://www.virtualbox.org...
Page 2: Table Of Contents
Contents 1 Introduction Virtualization basics Software vs. hardware virtualization (VT-x and AMD-V) Features overview ......13 Supported host operating systems Supported guest operating systems 64-bit guests...
Page 3 3.4.2 Changing removable media 3.4.3 Saving the state of the machine 3.4.4 Snapshots ......42 The Virtual Disk Manager Deleting virtual machines Virtual machine settings...
Page 4 iSCSI servers ....... . . 80 5.5.1 Access iSCSI targets via Internal Networking 6 Virtual networking Virtual networking hardware Introduction to networking modes...
Page 5 8.14 VBoxManage createhd 8.15 VBoxManage modifyhd 8.16 VBoxManage clonehd 8.17 VBoxManage convertfromraw 8.18 VBoxManage addiscsidisk 8.19 VBoxManage getextradata/setextradata 8.20 VBoxManage setproperty 8.21 VBoxManage usbﬁlter add/modify/remove 8.22 VBoxManage sharedfolder add/remove 8.23 VBoxManage metrics 8.24 VBoxManage guestproperty 8.25 VBoxManage dhcpserver 9 Advanced topics VirtualBox conﬁguration data Automated Windows guest logons (VBoxGINA) Custom external VRDP authentication...
Page 6 11 Troubleshooting 11.1 General ........144 11.1.1 Collecting debugging information 11.1.2 Guest shows IDE errors for VDI on slow host ﬁle system 11.1.3 Responding to guest IDE ﬂush requests...
Page 7 12.10Version 2.0.4 (2008-10-24) 12.11Version 2.0.2 (2008-09-12) 12.12Version 2.0.0 (2008-09-04) 12.13Version 1.6.6 (2008-08-26) 12.14Version 1.6.4 (2008-07-30) 12.15Version 1.6.2 (2008-05-28) 12.16Version 1.6.0 (2008-04-30) 12.17Version 1.5.6 (2008-02-19) 12.18Version 1.5.4 (2007-12-29) 12.19Version 1.5.2 (2007-10-18) 12.20Version 1.5.0 (2007-08-31) 12.21Version 1.4.0 (2007-06-06) 12.22Version 1.3.8 (2007-03-14) 12.23Version 1.3.6 (2007-02-20) 12.24Version 1.3.4 (2007-02-12) 12.25Version 1.3.2 (2007-01-15) 12.26Version 1.2.4 (2006-11-16)
Page 8 14.2.7 Slirp license 14.2.8 liblzf license 14.2.9 libpng license 14.2.10lwIP license 14.2.11libxml license 14.2.12libxslt licenses 14.2.13gSOAP Public License Version 1.3a 14.2.14Chromium licenses 14.2.15curl license ......251 14.2.16dnsproxy license 15 VirtualBox privacy policy Glossary...
Page 9: Introduction
1 Introduction Sun VirtualBox is a collection of powerful virtual machine tools, targeting desktop computers, enterprise servers and embedded systems. With VirtualBox, you can virtu- alize 32-bit and 64-bit operating systems on machines with Intel and AMD processors, either by using hardware virtualization features provided by these processors or even entirely in software, at your option.
Page 10 ground, however, VirtualBox intercepts certain operations that the guest performs to make sure that the guest does not interfere with other programs on the host. The techniques and features that VirtualBox provides are useful for several scenar- ios: Operating system support. With VirtualBox, one can run software written for one operating system on another (for example, Windows software on Linux) without having to reboot to use it.
Page 11: Software Vs. Hardware Virtualization (Vt-X And Amd-V)
performance of the guest code on your machine, we had to go through a lot of optimizations that are speciﬁc to certain operating systems. So while your favorite operating system may run as a guest, we ofﬁcially support and optimize for a select few (which, however, include the most common ones).
Page 12 There are two ways in which VirtualBox can achieve virtualization: either entirely in software or, with newer processors, using certain hardware features. For some years, Intel and AMD processors have had support for so-called “hard- ware virtualization”. This means that these processors aid virtualization soft- ware such as VirtualBox in intercepting potentially dangerous operations that a guest operating system may be attempting and in presenting virtual hardware to a virtual machine.
Page 13: Features Overview
Warning: Do not run other hypervisors (open-source or commercial virtu- alization products) together with VirtualBox! While several hypervisors can normally be installed in parallel, do not attempt to run several virtual ma- chines from competing hypervisors at the same time. VirtualBox cannot track what another hypervisor is currently attempting to do on the same host, and especially if several products attempt to use hardware virtualization features such as VT-x, this can crash the entire host.
Page 14 1 Introduction Clean architecture; unprecedented modularity. VirtualBox has an extremely modular design with well-deﬁned internal programming interfaces and a clean separation of client and server code. This makes it easy to control it from several interfaces at once: for example, you can start a VM simply by clicking on a button in the VirtualBox graphical user interface and then control that machine from the command line, or even remotely.
Page 15 1 Introduction – Full ACPI support. The Advanced Conﬁguration and Power Interface (ACPI) is fully supported by VirtualBox. This eases cloning of PC images from real machines or third-party virtual machines into VirtualBox. With its unique ACPI power status support, VirtualBox can even report to ACPI- aware guest operating systems the power status of the host.
Page 16: Supported Host Operating Systems
1.4 Supported host operating systems Currently, VirtualBox is available for the following host operating systems: Windows hosts: – Windows XP, all service packs (32-bit) – Windows Server 2003 (32-bit) – Windows Vista (32-bit and 64-bit – Windows Server 2008 (32-bit and 64-bit) –...
Page 17: Supported Guest Operating Systems
Since VirtualBox is designed to provide a generic virtualization environment for x86 systems, it may run operating systems of any kind, even those that are not ofﬁcially supported by Sun Microsystems. However, our focus is to optimize the product’s per- formance for a select list of guest systems: Windows NT 4.0 All versions/editions and service packs are fully supported;...
Page 18: 64-Bit Guests
1.6 64-bit guests Starting with Version 2.0, VirtualBox also supports 64-bit guest operating systems. Starting with Version 2.1, you can even run 64-bit guests on a 32-bit host operating system, so long as you have sufﬁcient hardware. In particular, 64-bit guests are supported under the following conditions: 1.
Page 19: Installation
2 Installation As installation of VirtualBox varies depending on your host operating system, we pro- vide installation instructions in four separate chapters for Windows, Mac OS X, Linux and Solaris, respectively. 2.1 Installing on Windows hosts 2.1.1 Prerequisites For the various versions of Windows that we support as host operating systems, please refer to chapter 1.4, Supported host operating In addition, Windows Installer 1.1 or higher must be present on your system.
Page 20: Uninstallation
Networking This package contains extra networking drivers for your Windows host that VirtualBox needs to support Host Interface Networking (to make your VM’s virtual network cards accessible from other machines on your physical network). Depending on your Windows conﬁguration, you may see warnings about “unsigned drivers”...
Page 21: Uninstallation
2.2.2 Uninstallation To uninstall VirtualBox, open the disk image (dmg) ﬁle again and double-click on the uninstall icon contained therein. 2.2.3 Unattended installation To perform a non-interactive installation of VirtualBox you can use the command line version of the installer application. Mount the disk image (dmg) ﬁle as described in the normal installation.
Page 22 The VirtualBox kernel module is automatically installed on your system when you install VirtualBox. To maintain it with future kernel updates, for recent Linux distribu- tions – for example Fedora Core 5 and later, Ubuntu 7.10 (Gutsy) and later and Man- driva 2007.1 and later –, generally we recommend installing Dynamic Kernel Module Support (DKMS) .
Page 23: Usb And Advanced Networking Support
2. The kernel of your Linux host got updated. In that case, the kernel module will need to be reinstalled by executing (as root): /etc/init.d/vboxdrv setup 2.3.3 USB and advanced networking support In order to use VirtualBox’s USB support, the user account under which you intend to run VirtualBox must have read and write access to the USB ﬁlesystem (usbfs).
Page 24 sudo /etc/init.d/vboxdrv setup This will start a second attempt to build the module. If a suitable kernel module was found in the package or the module was successfully built, the installation script will attempt to load that module. If this fails, please see chapter 11.5.1, Linux kernel module refuses to Once VirtualBox has been successfully installed and conﬁgured, you can start it by...
Page 25 After that you need to put every user which should be able to use VirtualBox in the group vboxusers, either through the GUI user management tools or by running the following command as root: sudo usermod -a -G vboxusers username Note: The usermod command of some older Linux distributions does not support the -a option (which adds the user to the given group without affecting membership of other groups).
Page 26 make install The VirtualBox kernel module needs a device node to operate. The above make command will tell you how to create the device node, depending on your Linux system. The procedure is slightly different for a classical Linux setup with a /dev directory, a system with the now deprecated devfs and a modern Linux system with udev.
Page 27 sudo ./VirtualBox.run uninstall or as root ./VirtualBox.run uninstall . Starting with version 2.2.2, you can uninstall the .run package by invoking /opt/VirtualBox/uninstall.sh To manually uninstall VirtualBox, simply undo the steps in the manual installation in reverse order. 2.3.4.5 Automatic installation of Debian packages The Debian packages will request some user feedback when installed for the ﬁrst time.
Page 28: Starting Virtualbox On Linux
2.3.5 Starting VirtualBox on Linux The easiest way to start a VirtualBox program is by running the program of your choice (VirtualBox, VBoxManage, VBoxSDL or VBoxHeadless) from a terminal. These are symbolic links to VBox.sh that start the required program for you. The following detailed instructions should only be of interest if you wish to exe- cute VirtualBox without installing it ﬁrst.
Page 29: Starting Virtualbox On Solaris
Future versions of OpenSolaris may ship the VirtualBox kernel interface module, in which case you can remove this one before upgrading OpenSolaris. Next you should install the main VirtualBox package using: pkgadd -d VirtualBox-3.0.0-SunOS-x86.pkg Note: If you are using Solaris Zones, to install VirtualBox only into the current zone and not into any other zone, use pkgadd -G.
Page 30: Unattended Installation
2.4.4 Unattended installation To perform a non-interactive installation of VirtualBox we have provided a response ﬁle named autoresponse that the installer will use for responses to inputs rather than ask them from you. Extract the tar.gz package as described in the normal installation. Then open a root terminal session and execute: pkgadd -d VirtualBox-3.0.0-SunOS-x86 -n -a autoresponse SUNWvbox To perform a non-interactive uninstallation, open a root terminal session and exe-...
Page 31: Starting Out With Virtualbox
3 Starting out with VirtualBox As already mentioned in chapter 1.1, you to run each of your guest operating systems on its own virtual computer system, which is called a “virtual machine” (VM). The guest system will run in its VM as if it were installed on a real computer, according to the VM settings you have speciﬁed.
Page 32: Creating A Virtual Machine
3 Starting out with VirtualBox group of your “Applications” menu. Alternatively, you can type VirtualBox in a terminal. A window like the following should come up: On the left, you can see a pane that lists all the virtual machines you have created so far (quite a few in the example above).
Page 33 3 Starting out with VirtualBox On the following pages, the wizard will ask you for the bare minimum of information that is needed to create a VM, in particular: 1. A name for your VM, and the type of operating system (OS) you want to install. The name is what you will later see in the VirtualBox main window, and what your settings will be stored under.
Page 34 3 Starting out with VirtualBox Note: Choose this setting carefully! The memory you give to the VM will not be available to your host OS while the VM is running, so do not specify more than you can spare. For example, if your host machine has 1 GB of RAM and you enter 512 MB as the amount of RAM for a particular virtual machine, while that VM is running, you will only have 512 MB left for all the other software on your host.
Page 35 3 Starting out with VirtualBox The wizard allows you to create an image ﬁle or use an existing one. Note also that the disk images can be separated from a particular VM, so even if you delete a VM, you can keep the image, or copy it to another host and create a new VM for it there.
Page 36: Basics Of Virtual Machine Conﬁguration
3 Starting out with VirtualBox much more space, a ﬁxed-size ﬁle incurs less overhead and is therefore slightly faster than a dynamically expanding ﬁle. For details about the differences, please refer to chapter 5.2, (VDI, VMDK, VHD), page 77. To prevent your physical hard disk from running full, VirtualBox limits the size of the image ﬁle.
Page 37 3 Starting out with VirtualBox VM settings after installing a guest operating system, certain changes might prevent a guest operating system from functioning correctly if done after installation. Note: The “Settings” button is disabled while a VM is either in the “running” or “saved”...
Page 38: Running A Virtual Machine
3 Starting out with VirtualBox If you have downloaded installation media from the Internet in the form of an ISO image ﬁle (most probably in the case of a Linux distribution), you would normally burn this ﬁle to an empty CD or DVD and proceed as just described. With VirtualBox however, you can skip this step and mount the ISO ﬁle directly.
Page 39: Keyboard And Mouse Support In Virtual Machines
3 Starting out with VirtualBox in the window, as can be seen with the image in chapter 1.1, In general, you can use the virtual machine much like you would use a real com- puter. There are couple of points worth mentioning however. 3.4.1 Keyboard and mouse support in virtual machines 3.4.1.1 Capturing and releasing keyboard and mouse Since the operating system in the virtual machine does not “know”...
Page 40 3 Starting out with VirtualBox To release keyboard ownership, press the Host key (as explained above, typically the right Control key). Note that while the VM owns the keyboard, some key sequences (like Alt-Tab for example) will no longer be seen by the host, but will go to the guest instead. After you press the host key to re-enable the host keyboard, all key presses will go through the host again, so that sequences like Alt-Tab will no longer reach the guest.
Page 41: Changing Removable Media
3 Starting out with VirtualBox intercepted by the host operating system and therefore always switch terminals on the host. If, instead, you want to send these key combinations to the guest operating sys- tem in the virtual machine, you will need to use one of the following methods: –...
Page 42: Snapshots
3 Starting out with VirtualBox The difference between these three options is crucial. They mean: Save the machine state: With this option, VirtualBox “freezes” the virtual ma- chine by completely saving its state to your local disk. When you later resume the VM (by again clicking the “Start”...
Page 43: The Virtual Disk Manager
3 Starting out with VirtualBox Once you have set up the machine the way you want it, simply take a snapshot, and should anything happen to the installation, you can simply revert to its snapshot state. To take a snapshot of your VM, perform the following steps: 1.
Page 44 3 Starting out with VirtualBox The Disk Image Manager shows you all images that are currently registered with VirtualBox, conveniently grouped in three tabs for the three possible formats. These formats are: Hard disk images, either in VirtualBox’s own Virtual Disk Image (VDI) format or in the widely supported VMDK format CD/DVD images in standard ISO format;...
Page 45: Deleting Virtual Machines
3 Starting out with VirtualBox remove an image from the registry (and optionally delete the image ﬁle when doing so); “release” an image, that is, detach it from a virtual machine if it is currently attached to one as a virtual hard disk. We recommend that you maintain two special folders on your system for keeping images: one for hard disk image ﬁles (which can, in the case of dynamically expand- ing images, grow to considerable sizes), and one for ISO ﬁles (which were probably...
Page 46: General Settings
3 Starting out with VirtualBox 3.7.1 General settings In the Settings window, under “General”, you can conﬁgure the most fundamental aspects of the virtual machine such as memory and essential hardware. There are four tabs, “Basic”, “Advanced”, “Description” and “Other”. 3.7.1.1 “Basic”...
Page 47: System Settings
3 Starting out with VirtualBox 3.7.1.3 “Description” tab Here you can enter any description for your virtual machine, if you want. This has no effect of the functionality of the machine, but you may ﬁnd this space useful to note down things like the conﬁguration of a virtual machine and the software that has been installed into it.
Page 48 3 Starting out with VirtualBox Enable ACPI VirtualBox can present the Advanced Conﬁguration and Power Interface (ACPI) to the guest operating system for conﬁguring the virtual hardware. In addition, via ACPI, VirtualBox can present the host’s power status information to the guest.
Page 49: Display Settings
3 Starting out with VirtualBox In addition, the “Enable PAE/NX” setting determines whether the PAE and NX capa- bilities of the host CPU will be exposed to the virtual machine. PAE stands for “Physical Address Extension”. Normally, if enabled and supported by the operating system, then even a 32-bit x86 CPU can access more than 4 GB of RAM.
Page 50: Hard Disk Settings
3 Starting out with VirtualBox comes with Microsoft Windows (typically found under “Accessories” -> “Com- munication” -> “Remote Desktop Connection”) or, on Linux systems, the stan- dard open-source rdesktop program. These features are described in detail in chapter 7.4, (VRDP support), page 93.
Page 51: Cd/Dvd-Rom And Floppy Settings
3 Starting out with VirtualBox lifetime. You may, however, freely remove, add and exchange virtual hard drives after the machine has been set up. For example, if you wish to copy some ﬁles from another virtual disk that you created, you can connect that disk as a second hard disk. To connect an additional disk, double-click on the empty space in the list of virtual disks, or click on the respective icon to the right of that list.
Page 52: Audio Settings
3 Starting out with VirtualBox Note: The identiﬁcation string of the drive provided to the guest (which, in the guest, would be displayed by conﬁguration tools such as the Windows Device Manager) is always “VBOX CD-ROM”, irrespective of the current con- ﬁguration of the virtual drive.
Page 53: Serial Ports
3 Starting out with VirtualBox In most cases, this default setup will work ﬁne for you. However, VirtualBox is extremely ﬂexible in how it can virtualize networking. It supports up to eight virtual network cards per virtual machine, the ﬁrst four of which can be conﬁgured in detail in the graphical user interface.
Page 54: Usb Support
3 Starting out with VirtualBox You can elect to have the virtual serial port “disconnected”, which means that the guest will see it as hardware, but it will behave as if no cable had been connected to it. You can connect the virtual serial port to a physical serial port on your host.
Page 55 3 Starting out with VirtualBox Note: 1. Be careful with USB devices that are currently in use on the host! For example, if you allow your guest to connect to your USB hard disk that is currently mounted on the host, when the guest is activated, it will be disconnected from the host without a proper shutdown.
Page 56: Shared Folders
3 Starting out with VirtualBox 3. Remote. This setting speciﬁes whether the device will be local only, or remote only (over VRDP), or either. On a Windows host, you will need to unplug and reconnect a USB device to use it after creating a ﬁlter for it.
Page 57 3 Starting out with VirtualBox OVF is a cross-platform standard supported by many virtualization products which allows for creating ready-made virtual machines that can then be imported into a virtualizer such as VirtualBox. As opposed to other virtualization products, VirtualBox now supports OVF with an easy-to-use graphical user interface as well as using the command line.
Page 58 3 Starting out with VirtualBox This presents the virtual machines described in the OVF ﬁle and allows you to change the virtual machine settings by double-clicking on the description items. Once you click on “Import”, VirtualBox will copy the disk images and create local virtual ma- chines with the settings described in the dialog.
Page 59 3 Starting out with VirtualBox Note: OVF cannot describe every feature that VirtualBox provides for virtual machines. For example, snapshot information gets lost on export; the disk images will have a “ﬂattened” state identical to the current state of the virtual machine, but any snapshots that were deﬁned for the machine will have been merged.
Page 60: Guest Additions
4 Guest Additions The previous chapter covered getting started with VirtualBox and installing operating systems in a virtual machine. For any serious and interactive use, the VirtualBox Guest Additions will make your life much easier by providing closer integration between host and guest and improving the interactive performance of guest systems.
Page 61: Windows Guest Additions
For Linux and Solaris guests, the Xorg server version 1.3 or later is required for automatic resizing (the feature has been disabled on Fedora 9 guests due to a bug in the X server they supply). The server version can be checked with Xorg -version.
Page 62: Installing The Windows Guest Additions
Microsoft Windows Server 2003 (any service pack) Microsoft Windows Vista (all editions) Microsoft Windows 7 Beta Generally, it is strongly recommend to install the Windows Guest Additions. 4.2.1 Installing the Windows Guest Additions After mounting the Guest Additions ISO ﬁle, the Windows guest should automatically start the Guest Additions installer, which installs the Guest Additions into your Win- dows guest.
Page 63: Updating The Windows Guest Additions
4.2.1.2 Running the installer Unless you have the Autostart feature disabled in your Windows guest, Win- dows will now autostart the VirtualBox Guest Additions installation program from the Additions ISO. If the Autostart feature has been turned off, choose VBoxWindowsAdditions.exe from the CD/DVD drive inside the guest to start the installer.
Page 64: Manual File Extraction
4.2.4 Manual ﬁle extraction If you would like to install the ﬁles and drivers manually, you can extract the ﬁles from the Windows Guest Additions setup by typing: VBoxWindowsAdditions.exe /extract To explicitly extract the Windows Guest Additions for another platform than the current running one (e.g.
Page 65: Installing The Linux Guest Additions
Ubuntu 5.10, 6.06, 7.04, 7.10, 8.04, 8.10 and 9.04. Other distributions may work if they are based on comparable software releases. The version of the Linux kernel supplied by default in SUSE and openSUSE 10.2, Ubuntu 6.10 (all versions) and Ubuntu 6.06 (server edition) contains a bug which can cause it to crash during startup when it is run in a virtual machine.
Page 66: Video Acceleration And High Resolution Graphics Modes
sh ./VBoxAdditions.run help for more information. To recompile the guest kernel modules, use this command: /etc/init.d/vboxadd setup After compilation you should reboot your guest to ensure that the new modules are actually used. 4.3.2 Video acceleration and high resolution graphics modes In Linux guests, VirtualBox video acceleration is available through the X Window Sys- tem.
Page 67: Solaris Guest Additions
4.4 Solaris Guest Additions Like the Windows Guest Additions, the VirtualBox Guest Additions for Solaris take the form of a set of device drivers and system applications which may be installed in the guest operating system. The following Solaris distributions are ofﬁcially supported: OpenSolaris Nevada (Build 82 and higher;...
Page 68: Updating The Solaris Guest Additions
4.4.3 Updating the Solaris Guest Additions The Guest Additions should be updated by ﬁrst uninstalling the existing Guest Ad- ditions and then installing the new ones. Attempting to install new Guest Additions without removing the existing ones is not possible. 4.5 OS/2 Guest Additions VirtualBox also ships with a set of drivers that improve running OS/2 in a virtual machine.
Page 69 VBoxManage sharedfolder add "VM name" --name "sharename" --hostpath "C:\test" There are two types of shares: 1. VM shares which are only available to the VM for which they have been deﬁned; 2. transient VM shares, which can be added and removed at runtime and do not persist after a VM has stopped;...
Page 70: Seamless Windows
uid=5000(jack) gid=1(other) $mkdir /export/home/jack/mount $pfexec mount -F vboxfs -o uid=5000,gid=1 jackshare /export/home/jack/mount $cd ~/mount sharedfile1.mp3 sharedfile2.txt Beyond the standard options supplied by the mount command, the following are available: iocharset CHARSET to set the character set used for I/O operations (utf8 by default) and convertcp CHARSET to specify the character set used for the shared folder name (utf8 by default).
Page 71: Hardware 3D Acceleration (Opengl And Directx 8/9)
To enable seamless mode, after starting the virtual machine, press the Host key (nor- mally the right control key) together with “L”. This will enlarge the size of the VM’s display to the size of your host screen and mask out the guest operating system’s back- ground.
Page 72: Guest Properties
OpenGL on Linux requires kernel 2.6.27 and higher as well as X.org server version 1.5 and higher. Ubuntu 8.10 and Fedora 10 have been tested and conﬁrmed as working. OpenGL on Solaris guests requires X.org server version 1.5 and higher. 2.
Page 73 VM listed with their respective values, use this: $ VBoxManage guestproperty enumerate "Windows Vista III" VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Name: /VirtualBox/GuestInfo/OS/Product, value: Windows Vista Business Edition, timestamp: 1229098278843087000, flags: Name: /VirtualBox/GuestInfo/OS/Release, value: 6.0.6001,...
Page 74 $ VBoxManage guestproperty get "Windows Vista III" "/VirtualBox/GuestInfo/OS/Product" VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Value: Windows Vista Business Edition For more complex needs, you can use the VirtualBox programming interfaces; see...
Page 75: Virtual Storage
5 Virtual storage As the virtual machine will most probably expect to see a hard disk built into its virtual computer, VirtualBox must be able to present “real” storage to the guest as a virtual hard disk. There are presently three methods in which to achieve this: 1.
Page 76 5 Virtual storage CD-ROM/DVD drive, this leaves you with up to three virtual hard disks that you can attach to a virtual machine’s IDE controller. So even if your guest operating system has no support for SCSI or SATA devices, it should always be able to see the default IDE controller that is enabled by default.
Page 77: Disk Image Files (Vdi, Vmdk, Vhd)
To enable the SATA controller, on the “Hard Disks” page of a virtual machine’s settings dialog, check the “Enable Additional Controller” box and select “SATA (AHCI)“ from the list below. After this, the additional controller will appear as a separate PCI device in the virtual machine. Warning: The entire SATA controller and the virtual disks attached to it (in- cluding those in IDE compatibility mode) will only seen by operating systems that have device support for AHCI.
Page 78: Conﬁguring Image Write Operations
Finally, VirtualBox also fully supports the VHD format used by Microsoft. Irrespective of the disk format, as brieﬂy mentioned in chapter 3.2, machine, page 32, there are two options of how to create a disk image: ﬁxed-size or dynamically expanding. If you create a ﬁxed-size image of e.g.
Page 79 which VirtualBox creates automatically when the VM starts. The next time the VM is started, the differencing image is reset so that every time the VM starts, its immutable images have exactly the same content. If the automatic discarding of the differencing image on VM startup does not ﬁt your needs, you can turn it off using the autoreset parameter of VBoxManage modifyhd;...
Page 80: Cloning Disk Images
5.4 Cloning disk images You can duplicate hard disk image ﬁles on the same host to quickly produce a second virtual machine with the same operating system setup. However, you should only make copies of virtual disk images using the utility supplied with VirtualBox; see chapter 8.16, clonehd, page 118.
Page 81 which uses such an iSCSI target is done as described above. The only difference is that the IP address of the target must be speciﬁed as a numeric IP address. The IP stack accessing Internal Networking must be conﬁgured in the virtual ma- chine which accesses the iSCSI target.
Page 82: Virtual Networking
6 Virtual networking As brieﬂy mentioned in chapter 3.7.7, up to eight virtual PCI Ethernet cards for each virtual machine. For each such card, you can individually select 1. the hardware that will be virtualized as well as 2. the virtualization mode that the virtual card will be operating in with respect to your physical networking hardware on the host.
Page 83: Introduction To Networking Modes
VirtualBox has limited support for so-called jumbo frames, i.e. networking packets with more than 1500 bytes of data, provided that you use the Intel card virtualiza- tion and bridged networking. In other words, jumbo frames are not supported in NAT mode or with the AMD networking devices;...
Page 84: Not Attached" Mode
6.3 “Not attached” mode When a virtual network card’s mode is set to “Not attached”, VirtualBox reports to the guest that a network card is present, but that there is no connection – as if no Ethernet cable was plugged into the card. This way it is possible to “pull” the virtual Ethernet cable and disrupt the connection, which can be useful to inform a guest operating system that no network connection is available and enforce a reconﬁguration.
Page 85: Pxe Booting With Nat
To an application on the host or other physical (or virtual) machines on the network, it looks as though the service being proxied is actually running on the host (note that this also means that you cannot run the same service on the same ports on the host). However, you still gain the advantages of running the service in a virtual machine –...
Page 86: Bridged Networking
ICMP protocol limitations: Some frequently used network debugging tools (e.g. ping or tracerouting) rely on the ICMP protocol for sending/receiving messages. While ICMP support has been improved with VirtualBox 2.1 (ping should now work), some other tools may not work reliably. Receiving of UDP broadcasts is not reliable: The guest does not reliably receive broadcasts, since, in order to save resources, it only listens for a certain amount of time after the guest has sent UDP data on a particular port.
Page 87 Note: Even though TAP is no longer necessary on Linux with bridged network- ing, you can still use TAP interfaces for certain advanced setups, since you can connect a VM to any host interface – which could also be a TAP interface. To enable bridged networking, all you need to do is to open the Settings dialog of a virtual machine, go to the “Network”...
Page 88: Internal Networking
6.6 Internal networking Internal Networking is similar to bridged networking in that the VM can directly com- municate with the outside world. However, the “outside world” is limited to other VMs which connect to the same internal network. Even though technically, everything that can be done using internal networking can also be done using bridged networking, there are two good reasons why this additional mode was implemented: 1.
Page 89: Host-Only Networking
6.7 Host-only networking Host-only networking is another networking mode that was added with version 2.2 of VirtualBox. It can be thought of as a hybrid between the bridged and internal net- working modes: as with bridged networking, the virtual machines can talk to each other and the host as if they were connected through a physical ethernet switch.
Page 90: Alternative Front-Ends; Remote Virtual Machines
7 Alternative front-ends; remote virtual machines 7.1 Introduction As brieﬂy mentioned in chapter 1.3, ﬂexible internal design that allows you to use different front-ends to control the same virtual machines. To illustrate, you can, for example, start a virtual machine with VirtualBox’s easy-to-use graphical user interface and then stop it from the command line.
Page 91: Using Vboxmanage To Control Virtual Machines
7 Alternative front-ends; remote virtual machines 7.2 Using VBoxManage to control virtual machines This section will give you a brief introduction to VBoxManage and how you can use it to create and operate virtual machines. In essence, VBoxManage supports everything that our graphical user interface al- lows you to do with the click of a button.
Page 92: Vboxsdl, The Simpliﬁed Vm Displayer
7 Alternative front-ends; remote virtual machines $ VBoxManage createvm --name "SUSE 10.2" --register VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Virtual machine ’SUSE 10.2’ is created. UUID: c89fc351-8ec6-4f02-a048-57f4d25288e5 Settings file: ’/home/username/.VirtualBox/Machines/SUSE 10.2/SUSE 10.2.xml’...
Page 93: Remote Virtual Machines (Vrdp Support)
7 Alternative front-ends; remote virtual machines To start a virtual machine with VBoxSDL instead of the VirtualBox GUI, enter the following on a command line: VBoxSDL --startvm <vm> where <vm> is, as usual with VirtualBox command line parameters, the name or UUID of an existing virtual machine.
Page 94: Vboxheadless, The Vrdp-Only Server
7 Alternative front-ends; remote virtual machines hosts the default RDP port (3389) could be already used by the Windows RDP server, in this case you should choose another port for your VM(s). You should specify -N command line option with rdesktop to be able to use NumPad keys: rdesktop -N host_system_ip.
Page 95: Step By Step: Creating A Virtual Machine On A Headless Server
7 Alternative front-ends; remote virtual machines Note that when you use VBoxHeadless to start a VM, the built-in VRDP server will always be enabled, regardless of whether you have enabled the VRDP server in the VM’s settings. If this is undesirable (for example because you want to access the VM via ssh only), start the VM like this: VBoxHeadless --startvm <uuid|name>...
Page 96 7 Alternative front-ends; remote virtual machines 3. Create a virtual hard disk for the VM (in this case, 10GB in size) and register it with VirtualBox: VBoxManage createhd --filename "WinXP.vdi" --size 10000 --remember 4. Set this newly created VDI ﬁle as the ﬁrst virtual hard disk of the new VM: VBoxManage modifyvm "Windows XP"...
Page 97: Remote Usb
7 Alternative front-ends; remote virtual machines 7.4.3 Remote USB As a special feature on top of the VRDP support, VirtualBox supports remote USB devices over the wire as well. That is, the VirtualBox guest that runs on one computer can access the USB devices of the remote computer on which the RDP data is being displayed the same way as USB devices that are connected to the actual host.
Page 98: Rdp Encryption
7 Alternative front-ends; remote virtual machines – On Linux hosts, VRDPAuth.so authenticates users against the host’s PAM system. – On Windows hosts, VRDPAuth.dll authenticates users against the host’s WinLogon system. In other words, the “external” method per default performs authentication with the user accounts that exist on the host system.
Page 99: Vrdp Multiple Connections
7 Alternative front-ends; remote virtual machines 7.4.6 VRDP multiple connections The VirtualBox built-in RDP server supports simultaneous connections to the same running VM from different clients. All connected clients see the same screen output and share a mouse pointer and keyboard focus. This is similar to several people using the same computer at the same time, taking turns at the keyboard.
Page 100: Vboxmanage Reference
8 VBoxManage reference When running VBoxManage without parameters or when supplying an invalid com- mand line, the below syntax diagram will be shown. Note that the output will be slightly different depending on the host platform; when in doubt, check the output of VBoxManage for the commands available on your particular host.
Page 101 8 VBoxManage reference VBoxManage import (run with -n to have options displayed for a particular OVF) VBoxManage export VBoxManage startvm [--biosbootmenu disabled|menuonly|messageandmenu] [--biossystemtimeoffset <msec>] [--biospxedebug on|off] [--boot<1-4> none|floppy|dvd|disk|net>] [--hd<a|b|d> none|<uuid>|<filename>] [--idecontroller PIIX3|PIIX4] [--dvd none|<uuid>|<filename>|host:<drive>] [--dvdpassthrough on|off] [--floppy disabled|empty|<uuid>| <filename>|host:<drive>] [--nic<1-N> none|null|nat|bridged|intnet] [--nictype<1-N>...
Page 102 8 VBoxManage reference VBoxManage controlvm VBoxManage discardstate VBoxManage adoptstate VBoxManage snapshot VBoxManage openmedium VBoxManage closemedium VBoxManage showhdinfo VBoxManage createhd VBoxManage modifyhd VBoxManage clonehd [--type gui|sdl|vrdp|headless] <uuid>|<name> pause|resume|reset|poweroff|savestate| acpipowerbutton|acpisleepbutton| keyboardputscancode <hex> [<hex> ...]| injectnmi| setlinkstate<1-N> on|off | usbattach <uuid>|<address> | usbdetach <uuid>|<address> | dvdattach none|<uuid>|<filename>|host:<drive>...
Page 103 8 VBoxManage reference VBoxManage convertfromraw VBoxManage convertfromraw VBoxManage addiscsidisk VBoxManage getextradata VBoxManage setextradata VBoxManage setproperty VBoxManage usbfilter VBoxManage usbfilter <filename> <outputfile> [--format VDI|VMDK|VHD] [--variant Standard,Fixed,Split2G,Stream,ESX] stdin <outputfile> <bytes> [--format VDI|VMDK|VHD] [--variant Standard,Fixed,Split2G,Stream,ESX] --server <name>|<ip> --target <target> [--port <port>] [--lun <lun>] [--encodedlun <lun>] [--username <username>] [--password <password>]...
Page 104 8 VBoxManage reference VBoxManage usbfilter VBoxManage sharedfolder VBoxManage sharedfolder VBoxManage vmstatistics VBoxManage metrics VBoxManage metrics VBoxManage metrics VBoxManage metrics VBoxManage dhcpserver VBoxManage dhcpserver Each time VBoxManage is invoked, only one command can be executed. However, a command might support several subcommands which then can be invoked in one sin- gle call.
Page 105: Vboxmanage List
8 VBoxManage reference 8.1 VBoxManage list The list command gives relevant information about your system and information about VirtualBox’s current settings. The following subcommands are available with VBoxManage list: vms lists all virtual machines currently registered with VirtualBox. By default this displays a compact list with each VM’s name and UUID;...
Page 106: Vboxmanage Registervm / Unregistervm
8 VBoxManage reference $ VBoxManage showvminfo "Windows XP" VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Name: Windows XP Guest OS: Other/Unknown UUID: 1bf3464d-57c6-4d49-92a9-a5cc3816b7e7 Config file: /home/username/.VirtualBox/Machines/Windows XP/Windows XP.xml Memory size: 128MB VRAM size:...
Page 107: Vboxmanage Createvm
8 VBoxManage reference 8.4 VBoxManage createvm This command creates a new XML virtual machine deﬁnition ﬁle. The --name <name> parameter is required and must specify the name of the machine. Since this name is used by default as the ﬁle name of the set- tings ﬁle (with the extension .xml) and the machine folder (a subfolder of the .VirtualBox/Machines folder), it must conform to your host operating system’s requirements for ﬁle name speciﬁcations.
Page 108 8 VBoxManage reference --pae on|off: This enables/disables PAE (see chapter 3.7.2.2, “Processor” tab, page 48). --hwvirtex on|off|default: This enables or disables the use of hardware virtualization extensions (Intel VT-x or AMD-V) in the processor of your host system; see chapter 1.2, Software vs.
Page 109: Storage Settings
8 VBoxManage reference 8.5.2 Storage settings The following storage settings are available through VBoxManage modifyvm: --hd<a|b|d> none|<uuid>|<filename>: This speciﬁes the settings for each of the three virtual hard disks that can be attached to a VM’s IDE con- troller (primary master and slave, and secondary slave; the secondary master is always reserved for the virtual CD/DVD drive).
Page 110: Networking Settings
8 VBoxManage reference --floppy disabled|empty|<uuid>|<filename>|host:<drive>: This is the ﬂoppy equivalent to the --dvd option described above. disabled completely disables the ﬂoppy controller, whereas empty keeps the ﬂoppy con- troller enabled, but without a media inserted. 8.5.3 Networking settings The following networking settings are available through VBoxManage modifyvm: --nic<1-N>...
Page 111: Serial Port, Audio, Clipboard, Vrdp And Usb Settings
8 VBoxManage reference --intnet<1-N> network: If internal networking has been enabled for a vir- tual network card (see the --nic option above; otherwise this setting has no effect), use this option to specify the name of the internal network (see chapter 6.6, networking, page 88).
Page 112: Vboxmanage Import
8 VBoxManage reference should be shared with the host; see chapter 3.7.1, requires that the Guest Additions be installed in the virtual machine. --vrdp on|off: With the VirtualBox graphical user interface, this enables or disables the built-in VRDP server. Note that if you are using VBoxHeadless (see chapter 7.4.1, VBoxHeadless, the VRDP-only is always enabled.
Page 113: Vboxmanage Export
8 VBoxManage reference VBoxManage import WindowsXp.ovf --dry-run Interpreting WindowsXp.ovf... Virtual system 0: 0: Suggested OS type: "WindowsXP" (change with "--vsys 0 --ostype <type>"; use "list ostypes" to list all) 1: Suggested VM name "Windows XP Professional_1" (change with "--vsys 0 --vmname <name>") 3: Number of CPUs (ignored): 1 4: Guest memory: 956 MB (change with "--vsys 0 --memory <MB>") 5: Sound card (appliance expects "ensoniq1371", can change on import)
Page 114: Vboxmanage Startvm
8 VBoxManage reference VMDK. See chapter 3.8, Importing and exporting virtual troduction to appliances. The export command is simple to use: list the machine (or the machines) that you would like to export to the same OVF ﬁle and specify the target OVF ﬁle after an additional --output or -o option.
Page 115: Vboxmanage Controlvm
8 VBoxManage reference 8.9 VBoxManage controlvm The controlvm subcommand allows you to change the state of a virtual machine that is currently running. The following can be speciﬁed: VBoxManage controlvm <vm> pause temporarily puts a virtual machine on hold, without changing its state for good. The VM window will be painted in gray to indicate that the VM is currently paused.
Page 116: Vboxmanage Discardstate
8 VBoxManage reference dvdattach inserts a DVD image into the virtual machine or connects it to the host DVD drive. With this command (as opposed to VBoxManage modifyvm), the image ﬁle does not ﬁrst have to be registered with VirtualBox. You can use VBoxManage list hostdvds to display all the drives found on the host and the names VirtualBox uses to access them.
Page 117: Vboxmanage Showhdinfo
8 VBoxManage reference Note: For compatibility with earlier versions of VirtualBox, the “registerim- age” and “unregisterimage” commands are also supported and mapped inter- nally to the “openmedium” and “closemedium” commands, respectively. Note however that when you unregister a hard disk image using VBoxManage, it will not be deleted from the host computer’s hard drive.
Page 118: Vboxmanage Modifyhd
8 VBoxManage reference remember Keep the destination image registered after it was successfully written. Note: For compatibility with earlier versions of VirtualBox, the “createvdi” command is also supported and mapped internally to the “createhd” com- mand. 8.15 VBoxManage modifyhd With the modifyhd command, you can change the type of an existing image between the normal, immutable and write-through modes;...
Page 119: Vboxmanage Convertfromraw
8 VBoxManage reference format Allow to choose a ﬁle format for the output ﬁle different from the ﬁle format of the input ﬁle. variant Allow to choose a ﬁle format variant for the output ﬁle. It is a comma- separated list of variant ﬂags. Not all combinations are supported, and specifying inconsistent ﬂags will result in an error message.
Page 120: Vboxmanage Addiscsidisk
8 VBoxManage reference 8.18 VBoxManage addiscsidisk The addiscsidisk command attaches an iSCSI network storage unit to VirtualBox. The iSCSI target can then be made available to and used by a virtual machine as though it were a standard write-through virtual disk image. This command has the following syntax: VBoxManage addiscsidisk --server <name>|<ip>...
Page 121: Vboxmanage Getextradata/Setextradata
VBoxManage getextradata Fedora5 installdate which would return VirtualBox Command Line Management Interface Version 3.0.0 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Value: 2006.01.01 8.20 VBoxManage setproperty This command is used to change global settings which affect the entire VirtualBox installation.
Page 122: Vboxmanage Usbﬁlter Add/Modify/Remove
8 VBoxManage reference 8.21 VBoxManage usbﬁlter add/modify/remove The usbfilter commands are used for working with USB ﬁlters in virtual machines, or global ﬁlters which affect the whole VirtualBox setup. Global ﬁlters are applied be- fore machine-speciﬁc ﬁlters, and may be used to prevent devices from being captured by any virtual machine.
Page 123 8 VBoxManage reference Metric data is collected and retained internally; it may be retrieved at any time with the VBoxManage metrics query subcommand. The data is available as long as the background VBoxSVC process is alive. That process terminates shortly after all VMs and frontends have been closed.
Page 124: Vboxmanage Guestproperty
8 VBoxManage reference Note: The query subcommand does not remove or “ﬂush” retained data. If you query often enough you will see how old samples are gradually being “phased out” by new samples. collect This subcommand sets the interval between taking two samples of metric data and the number of samples retained internally.
Page 125: Vboxmanage Dhcpserver
8 VBoxManage reference omitted, the property is deleted. With --flags you can optionally specify ad- ditional behavior (you can combine several by separating them with commas): – TRANSIENT: the value will not be stored with the VM data when the VM exits;...
Page 126 8 VBoxManage reference With --lowerip and --upperip, you can specify the lowest and highest IP address, respectively, that the DHCP server will hand out to clients. Finally, you must specify --enable or the the DHCP server will be created in the disabled state, doing nothing.
Page 127: Advanced Topics
9 Advanced topics 9.1 VirtualBox conﬁguration data For each system user, VirtualBox stores conﬁguration data in the user’s home directory, as per the conventions of the host operating system: On Windows, this is %HOMEDRIVE%%HOMEPATH%\.VirtualBox; typically something like C:\Documents and Settings\Username\.VirtualBox. On Mac OS X, this is $HOME/Library/VirtualBox.
Page 128: Automated Windows Guest Logons (Vboxgina)
machine called “Fedora 6” would, by default, have its settings saved in .VirtualBox/Machines/Fedora 6/Fedora 6.xml. more control over the ﬁle names used, you can create the machine using VBoxManage createvm with the --settingsfile option; see chapter 8.4, createvm, page 107. VBoxManage The virtual machine directory will be renamed if you change the machine name.
Page 129: Custom External Vrdp Authentication
Note: The VirtualBox GINA is implemented as a wrapper around the standard Windows GINA (MSGINA.DLL) so it will most likely not work correctly with 3rd party GINA modules. To set credentials, use the following command on a running VM: VBoxManage controlvm "Windows XP" setcredentials "John Doe"...
Page 130 External authentication is the most ﬂexible as the external handler can both choose to grant access to everyone (like the “null” authentication method would) and delegate the request to the guest authentication component. When delegating the request to the guest component, it will still be called afterwards with the option to override the result.
Page 131: Secure Labeling With Vboxsdl
reverse the order of byte 6 and 7. Using this conversion you will get identical results when converting the binary UUID to the string representation. The second arguments contains information about the guest authentication status. For the ﬁrst call, it is always set to VRDPAuthGuestNotAsked. In case the function returns VRDPAuthDelegateToGuest, a guest authentication will be attempted and another call to the method is made with its result.
Page 132: Custom Vesa Resolutions
Additions automatically provide the reduced video modes. Additionally, the VESA BIOS has been adjusted to duplicate its standard mode table with adjusted resolutions. The adjusted mode IDs can be calculated using the following formula: reduced_modeid = modeid + 0x30 For example, in order to start Linux with 1024 x 748 x 16, the standard mode 0x117 (1024 x 768 x 16) is used as a base.
Page 133: Multiple Monitors For The Guest
9.6 Multiple monitors for the guest VirtualBox allows the guest to use multiple virtual monitors. Up to sixty-four virtual monitors are supported. Note: 1. Multiple monitors currently work only with Windows XP guests, and Guest Additions must be installed, as the implementation resides in the Guest Additions video driver.
Page 134: Launching More Than 120 Vms On Solaris Hosts
to the VBoxSDL main thread (ﬁrst entry in the ps list). For example, when switching away to another VT and saving the virtual machine from this terminal, the following sequence can be used to make sure the VM is not saved with stuck modiﬁers: kill -usr1 <pid>...
Page 135: Using A Raw Host Hard Disk From A Guest
This sets up a serial port in the guest with the default settings for COM1 (IRQ 4, I/O address 0x3f8) and the Location setting assumes that this conﬁguration is used on a Windows host, because the Windows named pipe syntax is used. Keep in mind that on Windows hosts a named pipe must always start with \\.\pipe\.
Page 136: Access To Individual Physical Hard Disk Partitions
arbitrary ways without having to recreate the image ﬁle that gives access to the raw disk. To create an image that represents an entire physical hard disk (which will not contain any actual data, as this will all be stored on the physical disk), on a Linux host, use the command VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sda...
Page 137 VirtualBox uses the same partition numbering as your Linux host. As a result, the numbers given in the above example would refer to the ﬁrst primary partition and the ﬁrst logical drive in the extended partition, respectively. On a Windows host, instead of the above device speciﬁcation, use e.g. \\.\PhysicalDrive0.
Page 138: Allowing A Virtual Machine To Start Even With Unavailable Cd/Dvd/Floppy Devices
9.11 Allowing a virtual machine to start even with unavailable CD/DVD/ﬂoppy devices When, on VM startup, a CD, DVD or ﬂoppy device is unavailable, VirtualBox by default prints an error message and refuses to start the virtual machine. In some situations this behavior is not desirable.
Page 139: Tuning Tcp/Ip Buffers For Nat
VBoxManage setextradata "Linux Guest" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/NextServer" 10.0.2.2 VBoxManage setextradata "Linux Guest" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/BootFile" /srv/tftp/boot/MyPXEBoot.pxe 9.12.3 Tuning TCP/IP buffers for NAT The VirtualBox NAT stack performance is often determined by its interaction with the host’s TCP/IP stack and the size of several buffers (SO_RCVBUF and SO_SNDBUF). For certain setups users might want to adjust the buffer size for better performance.
Page 140: Enabling Dns Proxy In Nat Mode
9.12.5 Enabling DNS proxy in NAT mode For resolving network names the DHCP server of the NAT engine offers a list of regis- tered DNS servers of the host. For some reason you might need to hide the DNS server list, thereby forcing the VirtualBox NAT engine to react to changes in the host network settings, for example about the end of DHCP leases.
Page 141: Conﬁguring The Guest Time Stamp Counter (Tsc) To Reﬂect Guest Execution141
"Host BIOS Version" VBoxManage setextradata "My VM" "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseDate" "Host BIOS Release Date" VBoxManage setextradata "My VM" "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMajor" VBoxManage setextradata "My VM" "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMinor" VBoxManage setextradata "My VM" "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMajor" VBoxManage setextradata "My VM" "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" If a DMI string is not set, the default value of VirtualBox is used. To set an empty string use "<EMPTY>".
Page 142: Conﬁguring The Hard Disk Vendor Product Data (Vpd)
9.16 Conﬁguring the hard disk vendor product data (VPD) VirtualBox reports vendor product data for its virtual hard disks which consist of hard disk serial number, ﬁrmware revision and model number. These can be changed using the following commands: VBoxManage setextradata "My VM" "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber"...
Page 143: Virtualbox Programming Interfaces
10 VirtualBox programming interfaces VirtualBox comes with comprehensive support for third-party developers. The so- called “Main API” of VirtualBox exposes the entire feature set of the virtualization engine. It is completely documented and available to anyone who wishes to control VirtualBox programmatically.
Page 144: Troubleshooting
11 Troubleshooting This chapter provides answers to commonly asked questions. In order to improve your user experience with VirtualBox, it is recommended to read this section to learn more about common pitfalls and get recommendations on how to use the product. 11.1 General 11.1.1 Collecting debugging information For problem determination, it is often important to collect debugging information...
Page 145: Responding To Guest Ide Flush Requests
after a certain amount of data has been written. This interval is normally inﬁnite, but can be conﬁgured individually for each disk of a VM using the following command: VBoxManage setextradata VMNAME "VBoxInternal/Devices/piix3ide/0/LUN#[x]/Config/FlushInterval" [b] The value [x] that selects the disk is 0 for the master device on the ﬁrst channel, 1 for the slave device on the ﬁrst channel, 2 for the master device on the second channel or 3 for the master device on the second channel.
Page 146: Windows Guests
11.2 Windows guests 11.2.1 Windows bluescreens after changing VM conﬁguration Often, customers encounter Windows startup failures (the infamous “blue screen”) after performing conﬁguration changes to a virtual machine which are not allowed for an already installed Windows operating system. Depending on the presence of several hardware features, the Windows installation program chooses special kernel and device driver versions and will fail to startup should these hardware features be removed.
Page 147: How To Record Bluescreen Information From Windows Guests
VBoxManage setextradata VMNAME "VBoxInternal/Devices/piix3ide/0/Config/IRQDelay" 1 This sets the delay to one millisecond. In case this doesn’t help, increase it to a value between 1 and 5 milliseconds. Please note that this slows down disk performance. After installation, you should be able to remove the key (or set it to 0). 11.2.4 How to record bluescreen information from Windows guests When Windows guests run into a kernel crash, they display the infamous bluescreen.
Page 148: Amd Barcelona Cpus
11.3.2 AMD Barcelona CPUs Most Linux-based guests will fail with AMD Phenoms or Barcelona-level Opterons due to a bug in the Linux kernel. Enable the I/O-APIC to work around the problem (see chapter 3.7.1.2, “Advanced” tab, page 46). 11.3.3 Buggy Linux 2.6 kernel versions The following bugs in Linux kernels prevent them from executing correctly in VirtualBox, causing VM boot crashes: The Linux kernel version 2.6.18 (and some 2.6.17 versions) introduced a race...
Page 149: Cd/Dvd Changes Not Recognized
the COM server might experience an internal error and subsequently other processes fail to initialize it. In these situations, it is recommended to use the Windows task manager to kill the process VBoxSVC.exe. 11.4.2 CD/DVD changes not recognized In case you have assigned a physical CD/DVD drive to a guest and the guest does not notice when the medium changes, make sure that the Windows media change notiﬁcation (MCN) feature is not turned off.
Page 150: Running An Iscsi Initiator And Target On A Single System
11.4.4 Running an iSCSI initiator and target on a single system Deadlocks can occur on a Windows host when attempting to access an iSCSI target running in a guest virtual machine with an iSCSI initiator (e.g. Microsoft iSCSI Ini- tiator) that is running on the host. This is caused by a ﬂaw in the Windows cache manager component, and causes sluggish host system response for several minutes, followed by a “Delayed Write Failed”...
Page 151: Linux Host Cd/Dvd Drive Not Found (Older Distributions)
11.5.3 Linux host CD/DVD drive not found (older distributions) On older Linux distributions, if your CD/DVD device has a different name, VirtualBox may be unable to ﬁnd it. On older Linux hosts, VirtualBox performs the following steps to locate your CD/DVD drives: 1.
Page 152: Vboxsvc Ipc Issues
for IDE CD/DVD writer units this must refer to the appropriate SCSI CD-ROM device node (e.g. /dev/scd0) if the ide-scsi kernel module is loaded. This module is required for CD/DVD writer support with all Linux 2.4 kernels and some early 2.6 kernels. Many Linux distributions load this module whenever a CD/DVD writer is detected in the system, even if the kernel would support CD/DVD writers without the module.
Page 153: Pax/Grsec Kernels
Replace 85 with the group ID that matches your system (search /etc/group for “usb” or similar). Alternatively, if you don’t mind the security hole, give all users access to USB by changing “664” to “666”. The various distributions are very creative from which script the usbfs ﬁlesys- tem is mounted.
Page 154: Solaris Hosts
a weird error message such as “failed to mount the root partition”), then you have probably run into a memory conﬂict of your kernel and initial RAM disk. This can be solved by adding the following parameter to your GRUB conﬁguration: uppermem 524288 11.6 Solaris hosts 11.6.1 Cannot start VM, not enough contiguous memory...
Page 155: Change Log
12 Change log This section summarizes the changes between VirtualBox versions. Note that this change log is not exhaustive; not all changes are listed. VirtualBox version numbers consist of three numbers separated by dots where the ﬁrst number represents the major version, the 2nd number the minor version and the 3rd one the build number.
Page 156 12 Change log VMM: some Windows guests detected a completely wrong CPU frequency (bug #2227) VMM: ﬁxed hanging and unkillable VM processes (bug #4040) VMM: ﬁxed random infrequent guest crashes due XMM state corruption (Win64 hosts only) VMM: performance improvements for network I/O (VT-x/AMD-V only) GUI: added mini toolbar for fullscreen and seamless mode (Thanks to Huihong Luo) GUI: redesigned settings dialogs...
Page 157 12 Change log VHD: ﬁxed crash when discarding snapshots of a VHD image VHD: ﬁxed access beyond the block bitmap which could lead to arbitrary crashes VBoxManage: ﬁxed incorrect partition table processing when creating VMDK ﬁles giving raw partition access (bug #3510) VBoxManage: support cloning to existing image ﬁle OVF: several OVF 1.0 compatibility ﬁxes OVF: ﬁxed exporting of disk images when multiple virtual machines are exported...
Page 158: Version 2.2.4 (2009-05-29)
Web service: ﬁxed inability to handle NULL pointers for object arguments, which are valid values for a lot of APIs, in both the raw and the object-oriented web service. Web service: object-oriented bindings for JAX-WS did not exhibit interface inher- itance correctly, ﬁxed Web service: added support for IDisplay and IGuest interfaces, which were pre- viously unavailable...
Page 159 12 Change log OVF: ﬁxed potential crashes during import/export on Win64 hosts VBoxManage modifyhd --compact: ﬁxed bug which could lead to crashes and image corruption (bug #3864) VBoxManage metrics collect: now ﬂushes the output stream VHD: made VBoxManage internalcommands sethduuid work for .vhd ﬁles (bug #3443) VHD: some .vhd ﬁles could not be cloned (bug #4080) NAT: improvement of TCP connection establishment (bug #2987)
Page 160: Version 2.2.2 (2009-04-27)
12.3 Version 2.2.2 (2009-04-27) This is a maintenance release. The following items were ﬁxed and/or added: Host and guest clipboard: ﬁxed a number of issues affecting hosts and guests running the X window system Guest Additions: make sure the virtual mouse autodetection works on ﬁrst re- boot after installing the Additions on X.Org server 1.5 and later Guest Additions: properly report process identity number of running services Guest Additions: clean up properly if the X Window server terminates...
Page 161: Version 2.2.0 (2009-04-08)
VBoxManage modifyhd --compact: implemented again for VDI ﬁles, and now supports relative paths (bug #2180, #2833) VBoxManage snapshot discard: made it work again (2.1.0 regression; bug #3714) NAT: on some Windows hosts, the guest didn’t receive a DHCP lease (bug #3655) NAT: ﬁxed release assertion during poll() (bug #3667) Networking: ﬁxed a deadlock caused by the PCnet network device emulation (2.2.0 regression, bug #3676)
Page 162 12 Change log Shared Folders for Solaris and OpenSolaris guests OpenGL 3D acceleration for Linux and Solaris guests (see chapter 4.8, Hardware 8/9), page 71) 3D acceleration (OpenGL and DirectX Added C API in addition to C++, Java, Python and Web Services In addition, the following items were ﬁxed and/or added: VMM: FreeBSD guest related ﬁx for V86 ﬂags (bug #2342) VMM: ﬁxed guru meditation when booting an AsteriskNow Linux VM (bug...
Page 163 12 Change log USB: further reduced host CPU utilization for OHCI and EHCI; the “VBoxInternal/Devices/usb- ohci/0/Conﬁg/FrameRate” CFG key is no longer necessary and no longer sup- ported USB: ﬁxed BSOD on the host with certain USB devices (Windows hosts only; bug #1654) E1000: properly handle cable disconnects (bug #3421) VRDP: ﬁxed hangs when VRDP server is enabled or disabled in runtime...
Page 164 12 Change log VBoxManage: big command line processing cleanup, the legacy single-dash op- tions are deprecated and will be removed in the next major release, so switch to the new options now Hard disks: improved immutable disk support to auto-reset diff ﬁle at VM startup (related to bug #2772) GUI: enable the audio adapter by default for new VMs GUI: warn if VT-x/AMD-V is not operational when starting a 64-bit guest...
Page 165: Version 2.1.4 (2009-02-16)
12.5 Version 2.1.4 (2009-02-16) This is a maintenance release. The following items were ﬁxed and/or added: Windows hosts: ﬁxed host crashes/hangs on certain 32 bits Windows systems when running Linux guests (bugs #1606, #2269, #2763) Windows hosts: ﬁxed network component BSOD issue (bugs #3168, #2916) Windows hosts: ﬁxed installation issues (bugs #2517, #1730, #3130) Linux hosts: ﬁxed occasional kernel oopses (bug #2556) Linux hosts: ﬁxed module dependency for shipped modules (bug #3115)
Page 166 12 Change log NAT: ﬁxed occasional crashes when the guest is doing traceroute (non-Windows hosts; bug #3200) NAT: ﬁxed crashes under high load (bug #3110) NAT: ﬁxed truncated downloads (Windows hosts only, bug #3257) NAT: don’t intercept TFTP packages with a destination address different from the builtin TFTP server (bug #3112) USB: several ﬁxes for USB passthrough on Linux hosts USB: reduced host CPU utilization if EHCI is active...
Page 167: Version 2.1.2 (2009-01-21)
12.6 Version 2.1.2 (2009-01-21) This is a maintenance release. The following items were ﬁxed and/or added: USB: Linux host support ﬁxes (bug #3136) VMM: ﬁxed guru meditation for PAE guests on non-PAE hosts (AMD-V) VMM: ﬁxed guru meditation on Mac OS X hosts when using VT-x VMM: allow running up to 1023 VMs on 64-bit hosts (used to be 127) VMM: several FreeBSD guest related ﬁxes (bugs #2342, #2341, #2761) VMM: ﬁxed guru meditation when installing Suse Enterprise Server 10U2 (VT-x...
Page 168 12 Change log VGA: signiﬁcant performance improvements when using VT-x/AMD-V on Mac OS X hosts VGA: better handling for VRAM offset changes (ﬁxes GRUB2 and Dos DOOM display issues) VGA: custom VESA modes with invalid widths are now rounded up to correct ones (bug #2895) IDE: ﬁxed ATAPI passthrough support (Linux hosts only;...
Page 169 12 Change log VBoxManage convertfromraw: added parameter checking and made it de- fault to creating VDI ﬁles; ﬁxed and documented format parameter (bug #2776) VBoxManage clonehd: ﬁxed garbled output image when creating VDI ﬁles (bug #2813) VBoxManage guestproperty: ﬁxed property enumeration (incorrect parame- ters/exception) VHD: ﬁxed error when attaching certain container ﬁles (bug #2768) Solaris hosts: added support for serial ports (bug #1849)
Page 170: Version 2.1.0 (2008-12-17)
Linux Additions: ﬁxed bug which prevented to properly set fmode on mapped shared folders (bug #1776) Linux Additions: ﬁxed appending of ﬁles on shared folders (bug #1612) Linux Additions: ignore noauto option when mounting a shared folder (bug #2498) Linux Additions: ﬁxed a driver issue preventing X11 from compiling keymaps (bug #2793 and #2905) X11 Additions: workaround in the mouse driver for a server crash when the driver is loaded manually (bug #2397)
Page 171 12 Change log VMM: Solaris and OpenSolaris guest performance improvements for AMD-V (Barcelona family CPUs only) VMM: ﬁxed guru meditation while running the Dr. Web virus scanner (software virtualization only; bug #1439) VMM: deactivate VT-x and AMD-V when the host machine goes into suspend mode;...
Page 172: Version 2.0.8 (2009-03-10)
Graphics: ﬁxed handling of a guest video memory which is not a power of two (bug #2724) VBoxManage: ﬁxed bug which prevented setting up the serial port for direct device access VBoxManage: added support for VMDK and VHD image creation VBoxManage: added support for image conversion (VDI/VMDK/VHD/RAW) Solaris hosts: added IPv6 support between host and guest when using host in- terface networking...
Page 173: Version 2.0.6 (2008-11-21)
Networking: ﬁxed issue where a VM could lose connectivity after a reboot Linux hosts: ﬁxed occasional kernel oopses (bug #2556) Solaris hosts: ﬁxed high CPU load while running many guests in parallel Solaris hosts: ﬁxed inability to start more than 128 VMs Solaris/Web services: ﬁxed SMF script to set home directory correctly Linux Additions: ﬁxed occasional ﬁle corruption when writing ﬁles in O_APPEND mode to a shared folder (bug #2844)
Page 174: Version 2.0.4 (2008-10-24)
Linux hosts: ﬁxed assertion on high network load (AMD64 hosts, ﬁx for Linux distributions with glibc 2.6 and newer (bug #616) Linux hosts: don’t crash during shutdown with serial ports connected to a host device Solaris hosts: ﬁxed incompatibility between IPSEC and host interface networking Solaris hosts: ﬁxed a rare race condition while powering off VMs with host in- terface networking Solaris hosts: ﬁxed VBoxSDL on Solaris 10 by shipping the required SDL library...
Page 175 12 Change log VHD: ﬁxed bug which prevents booting from VHD images bigger than 4GB (bug #2085) VRDP: ﬁxed a repaint problem when the guest resolution was not equal to the client resolution Clipboard: don’t crash when host service initialization takes longer than ex- pected (Linux hosts only;...
Page 176: Version 2.0.2 (2008-09-12)
12.11 Version 2.0.2 (2008-09-12) This is a maintenance release. The following items were ﬁxed and/or added: VMM: ﬁxed inability to run more than one VM in parallel (AMD-V on CPUs with erratum 170 only; bug #2167) VMM: VT-x stability ﬁxes (bug #2179 and others) VMM: ﬁxed Linux 2.6.26+ kernel crashes (used by Ubuntu 8.10 Alpha, Fedora 10 Alpha;...
Page 177 12 Change log VRDP: allow a client to reconnect to an existing session on the VRDP server by dropping the existing connection (conﬁgurable and disabled by default; only relevant when multiconnection mode is disabled) VRDP: ﬁxed an image repaint problem Linux hosts: ﬁxed bug in vboxdrv.ko that could corrupt kernel memory and panic the kernel (bug #2078) Linux hosts: compile ﬁxes for kernel module on Linux 2.6.27...
Page 178: Version 2.0.0 (2008-09-04)
12.12 Version 2.0.0 (2008-09-04) This version is a major update. The following major new features were added: 64 bits guest support (64 bits host only) New native Leopard user interface on Mac OS X hosts The GUI was converted from Qt3 to Qt4 with many visual improvements New-version notiﬁer Guest property information interface Host Interface Networking on Mac OS X hosts...
Page 179: Version 1.6.6 (2008-08-26)
12.13 Version 1.6.6 (2008-08-26) This is a maintenance release. The following items were ﬁxed and/or added: VMM: ﬁxed excessive logging (bug #1901) VMM: AMD-V stability ﬁxes (bug #1685) GUI: added support for Ctrl+Caps reversed keyboards (bug #1891) SATA: ﬁxed BSODs of Windows guests on a SATA disk (bug #1941) SATA: ﬁxed hard disk detection on Solaris 10 U5 (bug #1789) VBoxHeadless: don’t start the clipboard service (bug #1743) VBoxHeadless: added -vrdp parameter which allows to start the VM session with-...
Page 180: Version 1.6.4 (2008-07-30)
Windows Additions: ﬁxed bug when creating intermediate directories (bug #1870) Windows Additions: implemented /xres=, /yres= and /depth= switches for the installer (bug #1990) Linux Additions: properly unregister the misc device when unloading the kernel module Linux Additions: ﬁxed startup order for recent Linux distributions again (e.g. openSUSE 11) Linux Additions: attempt to ﬁx the autostart issue of VBoxClient with Mandriva guests (bug #1699)
Page 181 12 Change log VRDP: ﬁxed enabling the RDP server during runtime VRDP: properly detect the rdesktop 1.6.0 RDP client VRDP: ﬁxed RDP crash (bug #1521) VRDP: updated modiﬁed rdesktop client to version 1.6.0 GUI: NLS improvements BIOS: added SMBIOS header to make Solaris and Vista recognize the DMI data ACPI: properly hide a disabled ﬂoppy controller VMM: small ﬁxes to protected mode without paging VMDK: ﬁxed handling of .vmdk images without UUIDs...
Page 182: Version 1.6.2 (2008-05-28)
12.15 Version 1.6.2 (2008-05-28) This is a maintenance release. The following items were ﬁxed and/or added: GUI: ﬁxed a bug which prevented to add more than one SATA drive from the GUI GUI: ﬁxed a regression introduced in 1.6.0: the fullscreen mode was left on every guest video mode switch GUI: ﬁxed several minor issues Networking: ﬁxed a host interface networking regression introduced in 1.6.0...
Page 183: Version 1.6.0 (2008-04-30)
Internal Networking: ﬁxed shutdown if more than two VMs are connected to the same network BIOS: allow to change the DMI information (see chapter 9.14, BIOS DMI information, page 140) RTC: ﬁxed UIP emulation to prevent jumping of time in Solaris guests Windows host: VirtualBox installation directory corrected for 64 bits Windows Windows host: ﬁxed VBoxVRDP.exe symlink Windows host: solved locking problems in raw partition VMDK support...
Page 184 12 Change log SATA hard disk (AHCI) controller (see chapter 5.1, Hard disk controllers: IDE, SATA (AHCI), SCSI, page 75) Experimental Physical Address Extension (PAE) support In addition, the following items were ﬁxed and/or added: GUI: added accessibility support (508) GUI: VM session information dialog VBoxHeadless: renamed from VBoxVRDP VMM: reduced host CPU load of idle guests...
Page 185: Version 1.5.6 (2008-02-19)
Shared Folders: many bugﬁxes to improve stability Seamless windows: added support for Linux guests Linux installer: support DKMS for compiling the kernel module Linux host: compatibility ﬁxes with Linux 2.6.25 Windows host: support for USB devices has been signiﬁcantly improved; many additional USB devices now work Windows Additions: automatically install AMD PCNet drivers on Vista guests Linux Additions: several ﬁxes, experimental support for RandR 1.2...
Page 186 12 Change log VMM: under heavy guest activity, for example when copying ﬁles to/from a shared folder, the VM could crash with an assertion VMM: added an option to select PIIX4 (improves compatibility with Windows guests created by VMware) VMM: ﬁxed a bug which could lead to memory corruption under rare circum- stances VMM: improved performance of Solaris guests VRDP: ﬁxed a 1.5.4 regression: VRDP client and server were out-of-sync if the...
Page 187: Version 1.5.4 (2007-12-29)
Linux installer: ﬁxed Slackware detection regression Linux installer: updated VBoxTunctl allowing to assign a tap device to a group on Linux kernels > 2.6.23 Windows Additions: several ﬁxes, in particular for Windows NT4 Windows Additions: made them uninstallable Linux Additions: ﬁxed installer for Kubuntu 8.04 Linux Additions: add default video mode for handling video mode hints from the host Linux host: compatibility ﬁxes with Linux >...
Page 188 12 Change log VMM: ﬁxed code for overriding CPUID values VMM: improved error handling on out-of-memory conditions API: don’t crash when trying to create a VM with a duplicate name API: don’t crash when trying to access the settings of a VM when some other VMs are not accessible API: ﬁxed several memory leaks ATA/IDE: ﬁxed SuSE 9.1 CD read installer regression...
Page 189: Version 1.5.2 (2007-10-18)
Clipboard: ﬁxed a SEGFAULT on VM exit (Linux host) Clipboard: ﬁxed a buffer overﬂow (Linux host) Shared Folders: ﬁxed memory leaks Linux installer: remove the old kernel module before compiling a new one Linux host: compatibility ﬁxes with Linux 2.6.24 Linux host: script ﬁxes for ArchLinux Linux host: load correct HAL library to determine DVD/ﬂoppy (libhal.so.1 not libhal.so)
Page 190 12 Change log GUI: ﬁxed DirectDraw mode with certain video cards (e.g. Intel i915) GUI: ﬁxed incorrect guest resolution after leaving fullscreen mode GUI: improved keyboard handling on Linux host GUI: show fatal VM aborts (aka “Guru Meditation”) GUI: ﬁxed crashes due to a display update race condition on some systems GUI: added ACPI shutdown option to the VM close dialog GUI: NLS improvements BIOS: ﬁxed ﬂoppy boot menu...
Page 191: Version 1.5.0 (2007-08-31)
IDE: large reads from CD could exceed the I/O buffer size Audio: load ALSA dynamically on Linux (i.e. do not fail when ALSA is not present) VRDP: support additional RDP clients (SunRay, WinConnect, Mac OS X) VRDP: ﬁxed issues when client color depth is higher than server color depth VRDP: make PAM authentication service name conﬁgurable VRDP: increased stack size to deal with stack consuming PAM library calls Additions: various ﬁxes and enhancements to clipboard handling...
Page 192 12 Change log In addition, the following items were ﬁxed and/or added: GUI: sometimes two mouse cursors were visible when Windows guest Additions became active GUI: added VT-x/AMD-V settings GUI: disable ’Show log...’ menu entry to prevent crash if VM list is empty GUI: the log window grabbed the keyboard GUI: ﬁxed error handling if Linux host clipboard initialization fails GUI: pass the Pause key and the PrtScrn key to the guest (Linux hosts)
Page 193 12 Change log VMM: ﬁxed crashes if memory allocation failed (Linux) VMM: ﬁxed enabling of Local APIC on AMD hosts (ﬁxed Ubuntu Feisty installa- tion kernel hang during boot) VMM: ﬁxed XFree86 4.3 (Debian/Sarge) segfaults when switching to text mode VMM: refuse to start when KVM is active (Linux Host) VMM: ﬁxed bootup hangs with ReactOS VMM: ﬁxed out-of-memory errors under certain environments with enough ap-...
Page 194: Version 1.4.0 (2007-06-06)
12 Change log Guest Additions: Linux guests shipping Xorg 1.3 (e.g. Fedora 7, Ubuntu Gutsy) are now supported Guest Additions: added DirectDraw support to the Windows display driver 12.21 Version 1.4.0 (2007-06-06) General: added support for OS X hosts General: added support for AMD64 hosts General: signed all executables and device drivers on Windows GUI: added user interface for Shared Folders GUI: added context menu for network adapters...
Page 195 12 Change log VMM: ﬁxed issues with V86 mode VMM: support V86 extensions (VME) VMM: support guests with a full GDT VMM: ﬁxed boot hangs for some Linux kernels VMM: improved FreeBSD and OpenBSD support VMM: improved performance of guests that aggressively patch kernel code (very recent Linux 2.6 kernels) VMM: added workaround for a design ﬂaw in AMD AM2 CPUs where the times- tamp counter shows large differences among CPU cores...
Page 196 12 Change log NAT: pass ﬁrst entry in DNS search list (Linux host) or primary DNS sufﬁx (Win- dows host) as domain name in DHCP NAT: support UDP broadcasts, which enables using Windows shares NAT: only warn if the name server could not be determined, no fatal error any- more NAT: ﬁx a potential problem with incorrect memory allocation Internal Networking: ﬁxed issue on Windows hosts...
Page 197: Version 1.3.8 (2007-03-14)
12 Change log Linux Additions: make VBox version visible in Linux modules with modinfo Linux Additions: make X11 guest video driver accept arbitrary X resolutions Linux Additions: make X11 setup work if /tmp uses a separate ﬁle system Linux Additions: better support unknown distributions Linux Installer: force a non-executable stack for all binaries and shared libraries Linux Installer: make it work on SELinux-enabled systems Linux Installer: ship VBoxTunctl...
Page 198: Version 1.3.6 (2007-02-20)
12 Change log Audio: ﬁxed crashes on Vista hosts NAT: allow conﬁguration of incoming connections (aka port mapping) Network: hard reset network device on reboot iSCSI: ﬁxed a hang of unpaused VMs accessing unresponsive iSCSI disks Linux Additions: support Xorg 7.2.x Linux Additions: ﬁxed default video mode if all other modes are invalid Linux Additions: set default DPI to 100,100 Linux Additions: ﬁxed initialization of video driver on X server reset...
Page 199: Version 1.3.4 (2007-02-12)
12 Change log 12.24 Version 1.3.4 (2007-02-12) General: ﬁxed unresolved symbol issue on Windows 2000 hosts General: added warnings at VirtualBox startup when there is no valid Linux kernel module General: ﬁxed problem with unrecognized host CDROM/DVD drives on Linux General: ﬁxed compatibility issue with SELinux GUI: improved USB user interface, easier ﬁlter deﬁnitions, menu to directly at- tach speciﬁc devices...
Page 200: Version 1.3.2 (2007-01-15)
12 Change log Network: ﬁxed IRQ conﬂict causing occasional major slowdowns with XP guests Network: signiﬁcantly improved send performance Audio: added mixer support to the AC’97 codec (master volume only) Audio: added support for ALSA on Linux (native, no OSS emulation) iSCSI: improved LUN handling iSCSI: ﬁxed hang due to packet overﬂow iSCSI: pause VM on iSCSI connection loss...
Page 201: Version 1.2.4 (2006-11-16)
VMM: signiﬁcant performance improvements for Linux 2.6 guests VMM: performance improvements for Windows guests Network: ﬁxed issues with DOS guests Network: ﬁxed creation of more than one host interface during process lifetime on Windows VBoxManage: added support for compacting VDI ﬁles (requires zeroing freespace in the guest) API: startup even when a VM conﬁguration ﬁle is inaccessible or corrupted API: faster startup using lazy media access checking...
Page 202: Version 1.1.12 (2006-11-14)
12 Change log VMM: experimental support for IBM OS/2 Warp (requires VT-x to be enabled) USB: added support for isochronous transfers (webcams, audio, etc.) USB: ﬁxed problem with devices not showing up after a guest reboot USB: ﬁxed several issues BIOS: ﬁxed use of fourth boot device BIOS: added boot menu support BIOS: added support for disks up to 2 Terabytes...
Page 203: Version 1.1.10 (2006-07-28)
12.29 Version 1.1.10 (2006-07-28) IDE: added workaround for Acronis TrueImage (violates IDE speciﬁcation) IDE: resolved issues with certain Linux guests ACPI: further improved host power status reporting API: ﬁxed several race conditions and improved reliability API: increased maximum guest RAM size to 2GB (Linux host) and 1.2GB (Win- dows host) USB: added option to set the OHCI timer rate VMM: ﬁxed several issues...
Page 204: Version 1.1.6 (2006-04-18)
VBoxManage: made VRDP authentication conﬁgurable VDI: added workaround against possible Windows host deadlocks caused by a synchronization ﬂaw in Windows ACPI: improved host power status reporting 12.31 Version 1.1.6 (2006-04-18) ACPI: added workaround for XP SP2 crash in intelppm.sys (the real problem is a bug in this driver) IDE: added support for image ﬁles of up to 8 terabytes API: ﬁxed several race conditions on SMP systems...
Page 205: Version 1.1.2 (2006-02-03)
VRDP: added client authentication through external authentication libraries (WinLogon and PAM interfaces are provided as sample code) VRDP: close TCP connection immediately when receiving bad data from the re- mote side VRDP: improved Microsoft RDP client support XPCOM: ﬁxed race condition on SMP systems that could lead to hung client processes (Linux host) API: ﬁxed race condition on SMP systems Network: added AMD PC-Net II 100MBit network card (Am79C973)
Page 206 12 Change log VMM: ﬁxed random user mode crashes with OpenBSD guests VMM: increased timing accuracy (PIT, RTC), reduced PIT query overhead VMM: tamed execution thread to make GUI more responsive (esp. when execut- ing real mode guest code such as bootloaders) VMM: signiﬁcant performance enhancements for OpenBSD guests VMM: several performance enhancements VMM: improved memory layout on Windows hosts to allow for large amounts of...
Page 207: Version 1.0.50 (2005-12-16)
12.34 Version 1.0.50 (2005-12-16) Note: Guest Additions have to be updated VMM: added support for OpenBSD guests VMM: ﬁxed a memory leak Network: added Internal Networking (to directly wire VMs without using host interfaces and making the trafﬁc visible on the host) Network: ﬁxed crash/hang at exit with TAP on Linux Graphics: added support for additional custom VESA modes Graphics: added support for VESA modes with y offset...
Page 208: Version 1.0.46 (2005-11-04)
GUI: allow creation and assignment of disk images in the New VM wizard. USB: ﬁxed high CPU load on certain Linux distributions VBoxSDL: ﬁxed several secure labeling issues (crash at exit, protection against guest video modes greater than what SDL provides on the host) VBoxManage: convert command line parameters from the current codepage to Unicode 12.36 Version 1.0.46 (2005-11-04)
Page 209: Version 1.0.42 (2005-08-30)
Graphics/Additions/GUI: added dynamic resizing support Graphics: added workaround for buggy VESA support in Windows Vista/Longhorn VRDP: performance and stability improvements; added support for graphics ac- celeration architecture USB: restructured USB subsystem; added support for ﬁlters to autocapture de- vices that meet deﬁned criteria GUI: added mouse wheel support VMM: added support for PAE host mode 12.38 Version 1.0.42 (2005-08-30)
Page 210: Version 1.0.40 (2005-06-17)
VBoxManage: restructured commands, added numerous improvements GUI: propagate hostkey change to all running instances GUI: perform image access tests asynchronously GUI: added boot order support GUI: user interface redesign 12.39 Version 1.0.40 (2005-06-17) Note: The conﬁguration has to be deleted as the format has changed. On Linux, issue rm -rf ˜...
Page 211: Version 1.0.39 (2005-05-05)
GUI: added detailed error information dialogs GUI: special handling of inaccessible media API: better error message handling, provide system parameters, handle inacces- sible media Guest Additions: implemented full pointer shape support for all pointer color depths including alpha channel VBoxManage: several command extensions 12.40 Version 1.0.39 (2005-05-05) Note: Guest Additions have to be updated.
Page 212: Version 1.0.37 (2005-04-12)
VMM: ﬁxed several crashes and hangs while installing certain builds of Windows 2000 and XP VMM: allow guests to have more than 512MB of RAM VMM: resolved compatibility issues with SMP systems (Windows Host) VRDP: process cleanup on Linux ﬁxed Linux module: ﬁxed build error on Red Hat 2.4.21-15-EL NT Additions: ﬁxed installation and a trap Win2k/XP Additions: ﬁxed installation...
Page 213: Known Limitations
13 Known limitations The following section describes some issues that are known not to work in VirtualBox 3.0.0. Unless marked otherwise these issues are planned to be ﬁxed in later releases. The following Guest SMP (multiprocessor) limitations exist: – Bad performance with 32-bit guests on AMD CPUs. This affects mainly Windows and Solaris guests, but possibly also some Linux kernel revisions.
Page 214 13 Known limitations – OVA archives (TAR containers) are not yet supported. – Remote ﬁles via HTTP or other mechanisms are not yet supported. Host-only networking. Creation/deletion of host-only adapters are supported for Windows hosts only presently. On other platforms, there is one ﬁxed host- only interface called “vboxnet0”...
Page 215 13 Known limitations – No ACPI information (battery status, power source) is reported to the guest. – No support for using wireless with bridged networking. – On Solaris 10 U4, zones are not supported. Guest Additions for OS/2. Shared folders are not yet supported with OS/2 guests.
Page 216: Third-Party Licenses
14 Third-party licenses VirtualBox incorporates materials from several Open Source software projects. There- fore the use of these materials by VirtualBox is governed by different Open Source licenses. This document reproduces these licenses and provides a list of the materials used and their respective licensing conditions.
Page 217 14 Third-party licenses VirtualBox may contain NSPR and XPCOM which is governed by the license in chapter 14.2.3, Mozilla Public License Copyright (C) The Authors. VirtualBox contains Slirp which is governed by the license in chapter 14.2.7, Slirp license, page and was written by Danny Gasparovski.
Page 218: Gnu General Public License (Gpl)
VirtualBox may contain code from the gSOAP XML web services tools, which are licensed under the license in chapter 14.2.13, page Copyright (C) 2000-2007, Robert van Engelen, Genivia Inc., and others. VirtualBox may ship with the application tunctl (shipped as VBoxTunctl) from the User-mode Linux suite which is governed by the license in chapter 14.2.1, GNU General Public License Copyright (C) 2002 Jeff Dike.
Page 219 source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights.
Page 220 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modiﬁcations or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modiﬁed ﬁles to carry prominent notices stating that you changed the ﬁles and the date of any change.
Page 221 tion and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making mod- iﬁcations to it.
Page 222 It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices.
Page 223: Gnu Lesser General Public License (Lgpl)
OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Page 224 To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modiﬁed by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author’s reputation will not be affected by problems that might be introduced by others.
Page 225 0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called “this License”).
Page 226 (For example, a function in a library to compute square roots has a purpose that is entirely well-deﬁned independent of the application. Therefore, Subsection 2d re- quires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still com- pute square roots.) These requirements apply to the modiﬁed work as a whole.
Page 227 rather than a “work that uses the library”. The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a “work that uses the Library” uses material from a header ﬁle that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not.
Page 228 e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the “work that uses the Library” must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs,...
Page 229 other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.
Page 230: Mozilla Public License (Mpl)
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
Page 231 A. Any addition to or deletion from the contents of a ﬁle containing Original Code or previous Modiﬁcations. B. Any new ﬁle that contains any part of the Original Code or previous Modiﬁcations. 1.10. “Original Code” means Source Code of computer software code which is de- scribed in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.
Page 232 the Modiﬁcations created by such Contributor (or portions thereof) either on an un- modiﬁed basis, with other Modiﬁcations, as Covered Code and/or as part of a Larger Work; and (b) under Patent Claims infringed by the making, using, or selling of Modiﬁcations made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modiﬁcations made by that Contributor (or...
Page 233 3.4. Intellectual Property Matters (a) Third Party Claims. If Contributor has knowledge that a license under a third party’s intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text ﬁle with the Source Code distribution titled “LEGAL”...
Page 234 Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. 3.7. Larger Works. You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product.
Page 235 CENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. 8. TERMINATION. 8.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach.
Page 236 LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIA- BILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEG- LIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU.
Page 237: X Consortium License (X11)
The Initial Developer of the Original Code is ________________________. Portions created by ______________________ are Copyright (C) ______ _______________________. All Rights Reserved. Contributor(s): ______________________________________. Alternatively, the contents of this ﬁle may be used under the terms of the _____ license (the “[___] License”), in which case the provisions of [______] License are applicable instead of those above.
Page 238: Openssl License
3. This notice may not be removed or altered from any source distribution. Jean-loup Gailly Mark Adler jloup@gzip.org madler@alumni.caltech.edu 14.2.6 OpenSSL license This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscape’s SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to.
Page 239: Liblzf License
The licence and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.] 14.2.7 Slirp license Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met: 1.
Page 240: Libpng License
CLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SER- VICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOW- EVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Page 241: Libxslt Licenses
VICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOW- EVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Page 242: Gsoap Public License Version 1.3A
IN NO EVENT SHALL THE DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHER- WISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of Daniel Veillard shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from him.
Page 243 1.5. “Executable” means Covered Code in any form other than Source Code. 1.6. “Initial Developer” means the individual or entity identiﬁed as the Initial Devel- oper in the Source Code notice required by Exhibit A. 1.7. “Larger Work” means a work which combines Covered Code or portions thereof with code not governed by the terms of this License.
Page 244 (b) under patents now or hereafter owned or controlled by Initial Developer, to make, have made, use and sell (“offer to sell and import”) the Original Code, Modiﬁ- cations, or portions thereof, but solely to the extent that any such patent is reasonably necessary to enable You to utilize, alone or in combination with other software, the Original Code, Modiﬁcations, or any combination or portions thereof.
Page 245 (a) Third Party Claims. If Contributor has knowledge that a license under a third party’s intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text ﬁle with the Source Code distribution titled “LEGAL”...
Page 246 3.8. Restrictions. You may not remove any product identiﬁcation, copyright, propri- etary notices or labels from gSOAP. 4 INABILITY TO COMPLY DUE TO STATUTE OR REGULATION. If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible;...
Page 247 OR NATURE WHATSOEVER, WHETHER BASED ON CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY OR OTHERWISE, ARISING OUT OF OR IN ANY WAY RELATED TO THE SOFTWARE, EVEN IF THE AUTHORS HAVE BEEN ADVISED ON THE POSSIBILITY OF SUCH DAMAGE OR IF SUCH DAMAGE COULD HAVE BEEN REASONABLY FORESEEN, AND NOTWITHSTANDING ANY FAIL- URE OF ESSENTIAL PURPOSE OF ANY EXCLUSIVE REMEDY PROVIDED.
Page 248 TIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COV- ERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAM- AGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES.
Page 249: Chromium Licenses
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CON- SEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSI- NESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,...
Page 250 Copyright (c) 2002, The Regents of the University of California. Produced at the Lawrence Livermore National Laboratory For details, contact: Randall Frank (rjfrank@llnl.gov). UCRL-CODE-2002-058 All rights reserved. This ﬁle is part of Chromium. For details, see accompanying documentation. Redistribution and use in source and binary forms, with or without modiﬁcation, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the disclaimer below.
Page 251: Curl License
14.2.14.3 COPYRIGHT.REDHAT ﬁle This Chromium distribution contains information and code which is covered under the following notice: Copyright 2001,2002 Red Hat Inc., Durham, North Carolina. All Rights Reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation ﬁles (the “Software”), to deal in the Software without restriction, including without limitation on the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to per-...
Page 252: Dnsproxy License
14.2.16 dnsproxy license Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation ﬁles (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit per- sons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies...
Page 253: Virtualbox Privacy Policy
15 VirtualBox privacy policy Policy version 1.3, June 29, 2009 This privacy policy sets out how Sun Microsystems, Inc. (“Sun”) treats personal information related to the virtualbox.org website and the VirtualBox registration pro- cess. § 1 virtualbox.org. The “virtualbox.org” website, as any other website, logs anony-...
Page 254 15 VirtualBox privacy policy § 6 Updates. Sun may update this privacy policy by posting a new version on the website. You should check this page occasionally to ensure you are happy with any changes.
Page 255: Glossary
Glossary ACPI Advanced Conﬁguration and Power Interface, an industry speciﬁcation for BIOS and hardware extensions to conﬁgure PC hardware and perform power manage- ment. Windows 2000 and higher as well as Linux 2.4 and higher support ACPI. Windows can only enable or disable ACPI support at installation time. AHCI Advanced Host Controller Interface, the interface that supports SATA devices such as hard disks.
Page 256 COM Microsoft Component Object Model, a programming infrastructure for modular software. COM allows applications to provide application programming inter- faces which can be accessed from various other programming languages and applications. VirtualBox makes use of COM both internally and externally to provide a comprehensive API to 3rd party developers.
Page 257 iSCSI Internet SCSI; see chapter 5.5, MAC Media Access Control, a part of an Ethernet network card. A MAC address is a 6-byte number which identiﬁes a network card. It is typically written in hexadecimal notation where the bytes are separated by colons, such as 00:17:3A:5E:CB:08.
Page 258 which data is transferred in both directions. Typically graphics updates and au- dio are sent from the remote machine and keyboard and mouse input events are sent from the client. VirtualBox contains an enhanced implementation of the relevant standards called “VirtualBox RDP” (VRDP), which is largely compatible with Microsoft’s RDP implementation.
Page 259 XML The eXtensible Markup Language, a metastandard for all kinds of textual infor- mation. XML only speciﬁes how data in the document is organized generally and does not prescribe how to semantically organize content. XPCOM Mozilla Cross Platform Component Object Model, a programming infrastruc- ture developed by the Mozilla browser project which is similar to Microsoft COM and allows applications to provide a modular programming interface.

Sun Microsystems VIRTUALBOX 3.0.0 User Manual

1 Introduction

2 Installation

3 Starting out with Virtualbox

4 Guest Additions

5 Virtual Storage

6 Virtual Networking

7 Alternative Front-Ends; Remote Virtual Machines

8 Vboxmanage Reference

9 Advanced Topics

10 Virtualbox Programming Interfaces

11 Troubleshooting

12 Change Log

13 Known Limitations

14 Third-Party Licenses

15 Virtualbox Privacy Policy

Glossary

Quick Links

User Manual

Need help?

Questions and answers

Related Manuals for Sun Microsystems VIRTUALBOX 3.0.0

Summary of Contents for Sun Microsystems VIRTUALBOX 3.0.0