VirtualBox
R
User Manual
Version 4.0.0
c 2004-2010 Oracle Corporation
1 First steps 9 1.1 Why is virtualization useful? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.2 Some terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1.3 Features overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.4 Supported host operating systems . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.5 Installing VirtualBox and extension packs . . . . . . . . . . . . . . . . . . . . . . 14 1.6 Starting VirtualBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 1.7 Creating your first virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . 16 1.8 Running your virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 1.8.1 Starting a new VM for the first time . . . . . . . . . . . . . . . . . . . . 19 1.8.2 Capturing and releasing keyboard and mouse . . . . . . . . . . . . . . 19 1.8.3 Typing special characters . . . . . . . . . . . . . . . . . . . . . . . . . . 20 1.8.4 Changing removable media . . . . . . . . . . . . . . . . . . . . . . . . . 21 1.8.5 Resizing the machine’s window . . . . . . . . . . . . . . . . . . . . . . 21 1.8.6 Saving the state of the machine . . . . . . . . . . . . . . . . . . . . . . 22 1.9 Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1.9.1 Taking, restoring and deleting snapshots . . . . . . . . . . . . . . . . . 23 1.9.2 Snapshot contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 1.10 Virtual machine configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 1.11 Removing virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 1.12 Importing and exporting virtual machines . . . . . . . . . . . . . . . . . . . . . 26 1.13 Alternative front-ends . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2 Installation details 29 2.1 Installing on Windows hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.1.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.1.2 Performing the installation . . . . . . . . . . . . . . . . . . . . . . . . . 29 2.1.3 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.1.4 Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.2 Installing on Mac OS X hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.1 Performing the installation . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.2 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.2.3 Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3 Installing on Linux hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3.2 The VirtualBox kernel module . . . . . . . . . . . . . . . . . . . . . . . 32 2.3.3 Performing the installation . . . . . . . . . . . . . . . . . . . . . . . . . 33 2.3.4 The vboxusers group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.5 Starting VirtualBox on Linux . . . . . . . . . . . . . . . . . . . . . . . . 36 2.4 Installing on Solaris hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.4.1 Performing the installation . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.4.2 Starting VirtualBox on Solaris . . . . . . . . . . . . . . . . . . . . . . . 37 2.4.3 Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 2.4.4 Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 2.4.5 Configuring a zone for running VirtualBox . . . . . . . . . . . . . . . . 38
2 Contents
4 Guest Additions 53 4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 4.2 Installing and Maintaining Guest Additions . . . . . . . . . . . . . . . . . . . . . 54 4.2.1 Guest Additions for Windows . . . . . . . . . . . . . . . . . . . . . . . . 54 4.2.2 Guest Additions for Linux . . . . . . . . . . . . . . . . . . . . . . . . . . 57 4.2.3 Guest Additions for Solaris . . . . . . . . . . . . . . . . . . . . . . . . . 62 4.2.4 Guest Additions for OS/2 . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.3 Shared folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.3.1 Manual mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 4.3.2 Automatic mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.4 Hardware-accelerated graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 4.4.1 Hardware 3D acceleration (OpenGL and Direct3D 8/9) . . . . . . . . . 65 4.4.2 Hardware 2D video acceleration for Windows guests . . . . . . . . . . . 66 4.5 Seamless windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.6 Guest properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 4.7 Guest control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 4.8 Memory overcommitment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4.8.1 Memory ballooning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 4.8.2 Page Fusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5 Virtual storage 72 5.1 Hard disk controllers: IDE, SATA (AHCI), SCSI, SAS . . . . . . . . . . . . . . . . 72 5.2 Disk image files (VDI, VMDK, VHD, HDD) . . . . . . . . . . . . . . . . . . . . . 74 5.3 The Virtual Media Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.4 Special image write modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 5.5 Differencing images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 5.6 Cloning disk images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 5.7 Host I/O caching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 5.8 Limiting bandwidth for disk images . . . . . . . . . . . . . . . . . . . . . . . . . 81
3 Contents
6 Virtual networking 84 6.1 Virtual networking hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 6.2 Introduction to networking modes . . . . . . . . . . . . . . . . . . . . . . . . . . 85 6.3 Network Address Translation (NAT) . . . . . . . . . . . . . . . . . . . . . . . . . 86 6.3.1 Configuring port forwarding with NAT . . . . . . . . . . . . . . . . . . 86 6.3.2 PXE booting with NAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.3.3 NAT limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 6.4 Bridged networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 6.5 Internal networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 6.6 Host-only networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8 VBoxManage 100 8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 8.2 Commands overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 8.3 VBoxManage list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 8.4 VBoxManage showvminfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 8.5 VBoxManage registervm / unregistervm . . . . . . . . . . . . . . . . . . . . . . 109 8.6 VBoxManage createvm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 8.7 VBoxManage modifyvm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 8.7.1 General settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 8.7.2 Networking settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 8.7.3 Serial port, audio, clipboard, remote desktop and USB settings . . . . . 114 8.7.4 Remote machine settings . . . . . . . . . . . . . . . . . . . . . . . . . . 115 8.7.5 Teleporting settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 8.8 VBoxManage import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 8.9 VBoxManage export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 8.10 VBoxManage startvm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 8.11 VBoxManage controlvm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 8.12 VBoxManage discardstate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 8.13 VBoxManage adoptstate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 8.14 VBoxManage snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 8.15 VBoxManage closemedium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 8.16 VBoxManage storageattach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 8.17 VBoxManage storagectl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 8.18 VBoxManage bandwidthctl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 8.19 VBoxManage showhdinfo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 8.20 VBoxManage createhd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
4 Contents
5 Contents
12 Troubleshooting 162 12.1 Procedures and tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 12.1.1 Categorizing and isolating problems . . . . . . . . . . . . . . . . . . . . 162 12.1.2 Collecting debugging information . . . . . . . . . . . . . . . . . . . . . 163 12.1.3 The built-in VM debugger . . . . . . . . . . . . . . . . . . . . . . . . . . 163 12.1.4 VM core format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 12.2 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 12.2.1 Guest shows IDE/SATA errors for file-based images on slow host file system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 12.2.2 Responding to guest IDE/SATA flush requests . . . . . . . . . . . . . . . 167 12.2.3 Poor performance caused by host power management . . . . . . . . . . 167 12.2.4 GUI: 2D Video Acceleration option is grayed out . . . . . . . . . . . . . 167 12.3 Windows guests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 12.3.1 Windows bluescreens after changing VM configuration . . . . . . . . . 168 12.3.2 Windows 0x101 bluescreens with SMP enabled (IPI timeout) . . . . . . 168 12.3.3 Windows 2000 installation failures . . . . . . . . . . . . . . . . . . . . 168 12.3.4 How to record bluescreen information from Windows guests . . . . . . 169 12.3.5 No networking in Windows Vista guests . . . . . . . . . . . . . . . . . . 169 12.3.6 Windows guests may cause a high CPU load . . . . . . . . . . . . . . . 169 12.3.7 Long delays when accessing shared folders . . . . . . . . . . . . . . . . 169 12.4 Linux and X11 guests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 12.4.1 Linux guests may cause a high CPU load . . . . . . . . . . . . . . . . . 169 12.4.2 AMD Barcelona CPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 12.4.3 Buggy Linux 2.6 kernel versions . . . . . . . . . . . . . . . . . . . . . . 170 12.4.4 Shared clipboard, auto-resizing and seamless desktop in X11 guests . . 170 12.5 Windows hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 12.5.1 VBoxSVC out-of-process COM server issues . . . . . . . . . . . . . . . . 170 12.5.2 CD/DVD changes not recognized . . . . . . . . . . . . . . . . . . . . . . 171 12.5.3 Sluggish response when using Microsoft RDP client . . . . . . . . . . . 171 12.5.4 Running an iSCSI initiator and target on a single system . . . . . . . . . 171 12.5.5 Bridged networking adapters missing . . . . . . . . . . . . . . . . . . . 172 12.5.6 Host-only networking adapters cannot be created . . . . . . . . . . . . 172 12.6 Linux hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 12.6.1 Linux kernel module refuses to load . . . . . . . . . . . . . . . . . . . . 172 12.6.2 Linux host CD/DVD drive not found . . . . . . . . . . . . . . . . . . . . 172 12.6.3 Linux host CD/DVD drive not found (older distributions) . . . . . . . . 173 12.6.4 Linux host floppy not found . . . . . . . . . . . . . . . . . . . . . . . . 173 12.6.5 Strange guest IDE error messages when writing to CD/DVD . . . . . . . 173 12.6.6 VBoxSVC IPC issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
6 Contents
7 Contents
Glossary 260
81 First stepsWelcomecomputer so that it can run multiple operating systems (inside multiple virtual machines) at thesame time. So, for example, you can run Windows and Linux on your Mac, run Windows Server2008 on your Linux server, run Linux on your Windows PC, and so on, all alongside your existingapplications. You can install and run as many virtual machines as you like – the only practicallimits are disk space and memory. VirtualBox is deceptively simple yet also very powerful. It can run everywhere from smallembedded systems or desktop class machines all the way up to datacenter deployments andeven Cloud environments. The following screenshot shows you how VirtualBox, installed on a Mac computer, is runningWindows 7 in a virtual machine window:
In this User Manual, we’ll begin simply with a quick introduction to virtualization and how toget 11.For existing VirtualBox users who just want to see what’s new in this release, there is a detailedlist in chapter 15, Change log, page 180.
9 1 First steps
•. •. •. • Infrastructure consolidation. Virtualization can significantly reduce hardware and elec- tricity costs. Most of the time, computers today only use a fraction of their potential power and run with low average system loads. A lot of hardware resources as well as electricity is thereby wasted. So, instead of running many such physical computers that are only par- tially used, one can pack many virtual machines onto a few powerful hosts and balance the loads between them.
Host operating system (host OS). This is the operating system of the physical computer on which VirtualBox was installed. There are versions of VirtualBox for Windows, Mac OS X, Linux and Solaris hosts; for details, please see chapter 1.4, Supported host operating systems, page, Win- dows, OS/2, FreeBSD, OpenBSD), but to achieve near-native performance of the guest code on your machine, we had to go through a lot of optimizations that are specific to certain operating systems. So while your favorite operating system may run as a guest, we
10 1 First steps
officially support and optimize for a select few (which, however, include the most common ones). See chapter 3.1, Supported guest operating systems, page 39 100. 53.
• Portability. VirtualBox runs on a large number of 32-bit and 64-bit host operating systems (again, see chapter 1.4, Supported host operating systems, page 13 for details). VirtualBox is a so-called “hosted” hypervisor (sometimes referred to as a “type 2” hypervi- sor).- ization Format (OVF, see chapter 1.12, Importing and exporting virtual machines, page 26), an industry standard created for this purpose. You can even import OVFs that were created with a different virtualization software. • 155. • Guest Additions: shared folders, seamless windows, 3D virtualization. The VirtualBox Guest Additions are software packages which can be installed inside of supported guest systems to improve their performance and to provide additional integration and communi- cation with the host system. After installing the Guest Additions, a virtual machine will sup- port automatic adjustment of video resolutions, seamless windows, accelerated 3D graphics and more. The Guest Additions are described in detail in chapter 4, Guest Additions, page 53.
11 1 First steps
In particular, Guest Additions provide for “shared folders”, which let you access files from the host system from within a guest machine. Shared folders are described in chapter 4.3, Shared folders, page 63.• cate- gories. For details, see chapter 3.10.1, USB settings, page 49. – Pro- grammable Interrupt Controller (I/O APIC), which is found in many modern PC sys- tems.screen virtu- alizing hard disks in container files. For details, see chapter 5.10, iSCSI servers, page 83. – PXE Network boot. The integrated virtual network cards of VirtualBox fully support remote booting via the Preboot Execution Environment (PXE).•.9, Snapshots, page 23. You can create and delete snapshots while the virtual machine is running.• chapter 1.13, Alternative front-ends, page 28 for details. Due to its modular architecture, VirtualBox can also expose its full functionality and con- figurability through a comprehensive software development kit (SDK), which allows for integrating every aspect of VirtualBox with other software systems. Please see chapter 11, VirtualBox programming interfaces, page 161 for details.
12 1 First steps
• 91. 95 for details. – USB over RDP. Via RDP virtual channel support, VirtualBox also allows you to connect arbitrary USB devices locally to a virtual machine which is running remotely on a VirtualBox RDP server; see chapter 7.1.4, Remote USB, page 94 for details.
• Windows hosts: – Windows XP, all service packs (32-bit) – Windows Server 2003 (32-bit) – Windows Vista (32-bit and 64-bit1 ). – Windows Server 2008 (32-bit and 64-bit) – Windows 7 (32-bit and 64-bit) • Mac OS X hosts:2 – 10.5 (Leopard, 32-bit) – 10.6 (Snow Leopard, 32-bit and 64-bit) Intel hardware is required; please see chapter 14, Known limitations, page 178 also. • Linux hosts (32-bit and 64-bit3 ). Among others, this includes: – Ubuntu). – Debian GNU/Linux 3.1 (“sarge”), 4.0 (“etch”), 5.0 (“lenny”) and 6.0 (“squeeze”) – Oracle Enterprise Linux 4 and 5 – Redhat Enterprise Linux 4, 5 and 6 – Fedora Core 4 to 14 – Gentoo Linux – SUSE Linux 9, 10 and 11, openSUSE 10.3, 11.0, 11.1, 11.2, 11.3 – Mandriva 2007.1, 2008.0, 2009.1, 2010.0 and 2010.11 Support for 64-bit Windows was added with VirtualBox 1.5.2 Preliminary Mac OS X support (beta stage) was added with VirtualBox 1.4, full support with 1.6. Mac OS X 10.4 (Tiger) support was removed with VirtualBox 3.1.3 Support for 64-bit Linux was added with VirtualBox 1.4.
13 1 First steps
It should be possible to use VirtualBox on most systems based on Linux kernel 2.6 using either the VirtualBox installer or by doing a manual installation; see chapter 2.3, Installing on Linux hosts, page 31. However, the formally tested and supported Linux distributions are those for which we offer a dedicated package. Note that starting with VirtualBox 2.1, Linux 2.4-based host operating systems are no longer supported. • Solaris hosts (32-bit and 64-bit) are supported with the restrictions listed in chapter 14, Known limitations, page 178: – Solaris 11 Express (Nevada build 86 and higher, OpenSolaris 2008.05 and higher) – Solaris 10 (u8 and higher) functional- ity: a) The virtual USB 2.0 (EHCI) device; see chapter 3.10.1, USB settings, page 49. b) VirtualBox Remote Desktop Protocol (VRDP) support; see chapter 7.1, Remote display (VRDP support), page 91. c) Intel PXE boot ROM with support for the E1000 network card. VirtualBox extension packages have a .vbox-extpack file name extension. To install an extension, simply double-click on the package file, and the VirtualBox Manager will guide you through the required steps. To view the extension packs that are currently installed, please start the VirtualBox Man- ager .34, VBoxMan- age extpack, page 133 for details.
• On a Windows host, in the standard “Programs” menu, click on the item in the “VirtualBox” group. On Vista or Windows 7, you can also type “VirtualBox” in the search box of the “Start” menu.
14 1 First steps
• On a Mac OS X host, in the Finder, double-click on the “VirtualBox” item in the “Applica- tions” folder. (You may want to drag this item onto your Dock.) •:
This window is called the “VirtualBox Manager”. On the left, you can see a pane that will laterlist all your virtual machines. Since you have not created any, the list is empty. A row of buttonsabove it allows you to create new VMs and work on existing VMs, once you have some. The paneon the right displays the properties of the virtual machine currently selected, if any. Again, sinceyou don’t have any machines yet, the pane displays a welcome message. To give you an idea what VirtualBox might look like later, after you have created many ma-chines, here’s another example:
15 1 First steps
On the following pages, the wizard will ask you for the bare minimum of information that isneeded to create a VM, in particular: 1. The VM name will later be shown in the VM list of the VirtualBox Manager window, and it will be used for the VM’s files on disk. Even though any name could be used, keep in un- usual that is not listed, select “Other”. Depending on your selection, VirtualBox will enable or disable certain VM settings that your guest operating system may require. This is partic- ularly important for 64-bit guests (see chapter 3.1.2, 64-bit guests, page 40)..
16 1 First steps 72:
17 1 First steps
• 74..
• select its entry in the list in the Manager window it and press the “Start” button at the top or •. Every-thing which would normally be seen on the virtual system’s monitor is shown in the window, ascan be seen with the image in chapter 1.2, Some terminology, page 10. In general, you can use the virtual machine much like you would use a real computer. Thereare couple of points worth mentioning however.
18 1 First steps
• operatingsystem.
19 1 First steps
• Your keyboard is owned by the VM if the VM window on your host desktop has the key- boardfor guest systems called the “VirtualBox Guest Additions” which make VM keyboard and mouseoperation a lot more seamless. Most importantly, the Additions will get rid of the second “guest”mouse pointer and make your host mouse pointer work directly in the guest. This will be described later in chapter 4, Guest Additions, page 53..
20 1 First steps: ∗ Host key + Del to send Ctrl+Alt+Del (to reboot the guest); ∗ Host key + Backspace to send Ctrl+Alt+Backspace (to restart the graphical user interface of a Linux or Solaris guest); ∗ Host key + F1 (or other function keys) to simulate Ctrl+Alt+F1 (or other func- tion”.
21 1 First steps
Please see chapter 14, Known limitations, page 178 53 for more information about the Guest Addi- tions. 3. Otherwise, if the window is bigger than the VM’s screen, the screen will be centered. If it is smaller, then scroll bars will be added to the machine window.
•). •.
• Power off the machine: With this option, VirtualBox also stops running the virtual ma- chine, but without saving its state..
22 1 First stepsstate. This has the same effect as powering it off, and the same warnings apply.
1.9 SnapshotsWith snapshots, you can save a particular state of a virtual machine for later use. At any latertime, you can revert to that state, even though you may have changed the VM considerably sincethen. A snapshot of a virtual machine is thus similar to a machine in “saved” state, as describedabove, but there can be many of them, and these saved states are preserved. You can see the snapshots of a virtual machine by first selecting a machine in the VirtualBoxManager and then clicking on the “Snapshots” button at the top right. Until you take a snapshotof the machine, the list of snapshots will be empty except for the “Current state” item, whichrepresents the “Now” point in the lifetime of the virtual machine.
1. You can take a snapshot. This makes a copy of the machine’s current state, to which you can go back at any given time later. • If your VM is currently running, select “Take snapshot” from the “Machine” pull-down menu of the VM window. •:
23 774.
24.
• 77. 78.).
•.
25 1 First stepsvarious settings that can be changed in the “Settings” window are described in detail in chapter3, Configuring virtual machines, page 39. Even more parameters are available with the VirtualBoxcommand line interface; see chapter 8, VBoxManage, page 100.
Note: The OVF standard is complex, and support in VirtualBox is an ongoing process. In particular, no guarantee is made that VirtualBox supports all appliances created by other virtualization software. For a list of known limitations, please see chapter 14, Known limitations, page 178.
5 OVF support was originally introduced with VirtualBox 2.2 and has seen major improvements with every version since.
26 1 First steps
1. They can come in several files, as one or several disk images, typically in the widely-used VMDK format (see chapter 5.2, Disk image files (VDI, VMDK, VHD, HDD), page 74).6Alternatively, select “File” -> “Import appliance” from the Manager window. In the file dialogthat comes up, navigate to the file with either the .ovf or the .ova file extension. If VirtualBox can handle the file, a dialog similar to the following will appear:
This presents the virtual machines described in the OVF file and allows you to change the vir-tual machine settings by double-clicking on the description items. Once you click on “Import”,VirtualBox will copy the disk images and create local virtual machines with the settings describedin the dialog. These will then show up in the Manager’s list of virtual machines. Note that since disk images tend to be big, and VMDK images that come with virtual appliancesare typically shipped in a special compressed format that is unsuitable for being used by virtualmachines directly, the images will need to be unpacked and copied first, which can take a fewminutes. For how to import an image at the command line, please see chapter 8.8, VBoxManage import,page 116. Conversely, to export virtual machines that you already have in VirtualBox, select “File” ->“Export appliance”. A different dialog window shows up that allows you to combine severalvirtual machines into an OVF appliance. Then, select the target location where the target filesshould be stored, and the conversion process begins. This can again take a while.6 Starting with version 4.0, VirtualBox creates file type associations for OVF and OVA files on your host operating system.
27 1 First steps
For how to export an image at the command line, please see chapter 8.9, VBoxManage export,page 117. 100. 3. VBoxSDL is an alternative, simple graphical front-end with an intentionally limited fea- ture 134.
4. Finally, VBoxHeadless is yet another front-end that produces no visible output on the host at all, but merely acts as a RDP server if the VirtualBox Remote Desktop Extension (VRDE) is installed. 92.
If the above front-ends still do not satisfy your particular needs, it is possible to create yet anotherfront-end to the complex virtualization engine that is the core of VirtualBox, as the VirtualBoxcore neatly exposes all of its features in a clean API; please refer to chapter 11, VirtualBoxprogramming interfaces, page 161.
282 Installation detailsAs installation of VirtualBox varies depending on your host operating system, we provide instal-lation instructions in four separate chapters for Windows, Mac OS X, Linux and Solaris, respec-tively.
• either by double-clicking on its executable file (contains both 32- and 64-bit architectures) •
In either case, this will display the installation welcome dialog and allow you to choose whereto install VirtualBox to and which components to install. In addition to the VirtualBox applica-tion, the following components are available:
USB support This package contains special drivers for your Windows host that VirtualBox re- quires 161). For this to work, an already working Windows Python installation on the system is required.1
Depending on your Windows configuration, you may see warnings about “unsigned drivers” orsimilar. Please select “Continue” on these warnings as otherwise VirtualBox might not functioncorrectly after installation.
29 2 Installation details
The installer will create a “VirtualBox” group in the Windows “Start” menu which allows youto launch the application and access its documentation. With standard settings, VirtualBox will be installed for all users on the local system. In casethis is not wanted, you have to invoke the installer by first extracting it by usingVirtualBox.exe -extract
ormsparameter to explicitly name the features to be installed. The following features are available:
Note: This feature must not be absent since it contains the minimum set of files to have working VirtualBox installation.
VBoxNetwork All networking support; includes the VBoxNetworkFlt and VBoxNetworkAdp fea- tures (see below).VBoxNetworkFlt Bridged networking support.VBoxNetworkAdp Host-only networking support.
For example, to only install USB support along with the main binaries, do a:VirtualBox.exe -msiparams ADDLOCAL=VBoxApplication,VBoxUSB
ormsiexec /i VirtualBox-<version>-MultiArch_<x86|amd64>.msi ADDLOCAL=VBoxApplication,VBoxUSB
2.1.3 UninstallationAs VirtualBox uses the standard Microsoft Windows installer, VirtualBox can be safely uninstalledat any time by choosing the program entry in the “Add/Remove Programs” applet in the WindowsControl Panel.
30 2 Installation details.
2.2.2 UninstallationTo uninstall VirtualBox, open the disk image (dmg) file again and double-click on the uninstallicon contained therein.
• Qt 4.4.0 or higher; • SDL 1.2.7 or higher (this graphics library is typically called libsdl or similar)..
31 2 Installation details
• On an Ubuntu system: sudo apt-get install dkms
• On a Fedora system: yum install dkms
• On a Mandriva system: urpmi dkms
If DKMS is available and installed, the VirtualBox kernel module should always work automat-ically, and it will be automatically rebuilt if your host kernel is updated. Otherwise, there are only two situations in which you will need to worry about the kernelmodule:. • With Debian and Ubuntu releases, you must install the right version of the linux-headers and if it exists the linux-kbuild package. Current Ubuntu releases should have the right packages installed by default. • In even older Debian and Ubuntu releases, you must install the right version of the kernel-headers package. • On Fedora and Redhat systems, the package is kernel-devel. • On SUSE and openSUSE Linux, you must install the right versions of the kernel-source and kernel-syms packages. • Alternatively, if you have built your own kernel, /usr/src/linux should point to your kernel sources. If you have not removed the files created during the build process, then your system will already be set up correctly. 2. The kernel of your Linux host was updated and DKMS is not installed. In that case, the kernel module will need to be reinstalled by executing (as root): /etc/init.d/vboxdrv setup
32 2 Installation details
You will be asked to accept the VirtualBox Personal Use and Evaluation License. Unless youanswer “yes” here, the installation will be aborted. The installer will also search for a VirtualBox kernel module suitable for your kernel. The pack-age includes pre-compiled modules for the most common kernel configurations. If no suitablekernel module is found, the installation script tries to build a module itself. If the build processis not successful you will be shown a warning and the package will be left unconfigured. Pleasehave a look at /var/log/vbox-install.log to find out why the compilation failed. You mayhave to install the appropriate Linux kernel headers (see chapter 2.3.2, The VirtualBox kernelmodule, page 32). After correcting any problems, dosudo /etc/init.d/vboxdrv setup
33 2 Installation details
The installer must be executed as root with either install or uninstall as the first parame-ter.sudo ./VirtualBox.run install
Or if you do not have the “sudo” command available, run the following as root instead:./VirtualBox.run install
After that you need to put every user which should be able to access USB devices fromVirtualBox guests in the group vboxusers, either through the GUI user management tools orby.
This will unpack all the files needed for installation in the directory install under the currentdirectory. The VirtualBox application files are contained in VirtualBox.tar.bz2 which you canunpack to any directory on your system. For example. To build themodule, change to the directory and issuemake
If everything builds correctly, issue the following command to install the module to the appro-priate module directory:sudo make install
In case you do not have sudo, switch the user account to root and performmake install
34 2 Installation details
The VirtualBox kernel module needs a device node to operate. The above make commandwill tell you how to create the device node, depending on your Linux system. The procedureis slightly different for a classical Linux setup with a /dev directory, a system with the nowdeprecated devfs and a modern Linux system with udev. On certain Linux distributions, you might experience difficulties building the module. You willhavebe ini-tialization script using the right method for your distribution. You should create VirtualBox’sconfiguration file:mkdir /etc/vboxecho INSTALL_DIR=/opt/VirtualBox > /etc/vbox/vbox.cfg
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 reverseorder.
The first line allows compilation of the vboxdrv kernel module if no module was found for thecurrent kernel. The second line allows the package to delete any old vboxdrv kernel modulescompiled by previous installations. These default settings can be applied withdebconf-set-selections vboxconf
35 2 Installation details
If the lineINSTALL_NO_VBOXDRV=1
is specified, the package installer will not try to build the vboxdrv kernel module if no modulefitting the current kernel was found.
Note that adding an active user to that group will require that user to log out and back inagain. This should be done manually after successful installation of the package.
36 2 Installation details
Starting with VirtualBox 3.1 the VirtualBox kernel package is no longer a separate packageand has been integrated into the main package. Install the VirtualBox package using:pkgadd -d VirtualBox-4.0.0 38.
The installer will then prompt you to enter the package you wish to install. Choose “1” or“all” and proceed. Next the installer will ask you if you want to allow the postinstall script tobe executed. Choose “y” and proceed as it is essential to execute this script which installs theVirtualBox kernel module. Following this confirmation the installer will install VirtualBox andexecute the postinstall setup script. Once the postinstall script has been executed your installation is now complete. You may nowsafely delete the uncompressed package and autoresponse files from your system. VirtualBoxwould be installed in /opt/VirtualBox.
2.4.3 UninstallationUninstallation of VirtualBox on Solaris requires root permissions. To perform the uninstallation,start a root terminal session and execute:pkgrm SUNWvbox
37 2 Installation details
Inside the zonecfg prompt add the device resource and match properties to the zone. Here’show it can be done:zonecfg:vboxzone>add devicezonecfg:vboxzone:device>set match=/dev/vboxdrvzonecfg:vboxzone:device>endzonecfg:vboxzone>verifyzonecfg:vboxzone>exit
If you are running VirtualBox 2.2.0 or above on Solaris 11 or Nevada hosts, you should adda device for /dev/vboxusbmon too, similar to what was shown above. This does not apply toSolaris 10 hosts due to lack of USB support. Replace “vboxzone” with the name of the zone in which you intend to run VirtualBox. Nextreboot the zone using zoneadm and you should be able to run VirtualBox from within the config-ured zone.
383 Configuring virtual machinesWhereas chapter 1, First steps, page 9 gave you a quick introduction to VirtualBox and how toget your first virtual machine running, the following chapter describes in detail how to configurevirtualcan present this image to a guest system as if it were a physical CD-ROM. Similarly, you can givea guest system access to the real network via its virtual network card, and, if you so choose, givethe host system, other guests, or computers on the Internet access to the guest system. in- stallation mechanisms not recommended. No Guest Additions available.Linux 2.4 Limited support.Linux 2.6 All versions/editions are fully supported (32 bits and 64 bits). Guest Additions are available. We strongly recommend using a Linux kernel version 2.6.13 or higher for better perfor- mance.
Note: Certain Linux kernel releases have bugs that prevent them from executing in a virtual environment; please see chapter 12.4.3, Buggy Linux 2.6 kernel versions, page 170.
39 3 Configuring virtual machines
OS/2 Warp 4.5 Requires hardware virtualization to be enabled. We officially support MCP2 only; other OS/2 versions may or may not work. Guest Additions are available with a limited feature set.1Mac OS X Server VirtualBox 3.2 added experimental support for Mac OS X Server guests, but this comes with restrictions. Please see the following section as well as chapter 14, Known limitations, page 178.
1. Mac OS X is commercial, licensed software and contains both license and technical re- strictions that limit its use to certain hardware and usage scenarios. It is important that you understand and obey these restrictions. In particular, for most versions of Mac OS X Server, Apple prohibits installing them on non- Apple hardware. Also, only the server versions of Mac OS X are designed to be used in a virtual environment; as a result, VirtualBox does not support client versions of Mac OS X as a guest. These license restrictions are also enforced on a technical level. Mac OS X Server verifies whether it is running on Apple hardware, and most DVDs that that come with Apple hard- ware even check for an exact model. These restrictions are not circumvented by VirtualBox and continue to apply.
2. Only CPUs known and tested by Apple are supported. As a result, if your Intel CPU is newer than the build of Mac OS X Server, or if you have a non-Intel CPU, it will most likely panic during bootup with an “Unsupported CPU” exception. It is generally best to use the Mac OS X Server DVD that came with your Apple hardware. 3. The Mac OS X Server Server support in VirtualBox is currently still experimental, please refer also to chapter 14, Known limitations, page 178.
1. You need a 64-bit processor with hardware virtualization support (see chapter 10.3, Hard- ware vs. software virtualization, page 155).
40 3 Configuring virtual machines
2. You must enable hardware virtualization for the particular VM for which you want 64-bit support; software virtualization is not supported for 64-bit VMs. 42. In addition, for 64-bit Windows guests, you should make sure that the VM uses the Intel networking device, since there is no 64-bit driver support for the AMD PCNet card; see chapter 6.1, Virtual networking hardware, page 84.
If you use the “Create VM” wizard of the VirtualBox graphical user interface (see chapter1.7, Creating your first virtual machine, page 16), VirtualBox will automatically use the correctsettings for each selected 64-bit operating system type.
41 3 Configuring virtual machines ma- chines. 16. Whereas the default settings of a newly created VM depend on the selected operating system type, changing the type later has no effect on VM settings; this value is then purely informational and decorative.
Mini toolbar In full screen or seamless mode, VirtualBox can display a small toolbar that con- tains.
42 3 Configuring virtual machines
Base memory This sets the amount of RAM that is allocated and given to the VM when it is running. The specified amount of memory will be requested from the host operating sys- tem, 16. If you select “Network”, the VM will attempt to boot from a network via the PXE mecha- nism. This needs to be configured in detail on the command line; please see chapter 8.7, VBoxManage modifyvm, page 110.Chipset Here you can select which chipset will be presented to the virtual machine. Before VirtualBox 4.0, PIIX3 was the only available option here. For modern guest operating systems such as Mac OS X server, that old chipset is no longer well supported. As a result, VirtualBox 4.0 introduced an emulation of the more modern ICH9 chipset, which supports PCI express, three PCI buses, PCI-to-PCI bridges and Message Signalled Interrupts (MSI). This allows modern operating systems to address more PCI devices and no longer requires IRQ sharing.Enable I/O APIC Advanced Programmable Interrupt Controllers (APICs) are a newer x86 hard- ware.
43 3 Configuring virtual machines
However, software support for I/O APICs has been unreliable with some operating sys- tems 51 for details.
Enable 19. This makes using the VM less tedious even if Guest Additions are not installed.3
In addition, you can turn off the Advanced Configuration and Power Interface (ACPI) whichVirtualBox presents to the guest operating system by default. ACPI is the current industry stan-dard to allow operating systems to recognize hardware, configure motherboards and other de-vices and manage power. As all modern PCs contain this feature and Windows and Linux havebeen supporting it for years, it is also enabled by default in VirtualBox. It can only be turned offon the command line; see chapter 8.7, VBoxManage modifyvm, page 110.
Warning: All Windows operating systems starting with Windows 2000 install different kernels depending on whether ACPI is available, so ACPI must not be turned off after installation of a Windows guest OS. Turning it on after installation will have no effect however.
3 Thevirtual USB tablet was added with VirtualBox 3.2. Depending on the guest operating system selected, this is now enabled by default for new virtual machines.
44 3 Configuring virtual machines
In addition, the “Enable PAE/NX” setting determines whether the PAE and NX capabilities ofthe 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 canaccess more than 4 GB of RAM. This is made possible by adding another 4 bits to memoryaddresses, so that with 36 bits, up to 64 GB can be addressed. Some operating systems (suchas Ubuntu Server) require PAE support from the CPU and cannot be run in a virtual machinewithout it. With virtual machines running modern server operating systems, VirtualBox also supports CPUhot-plugging. For details about this, please refer to chapter 9.4, CPU hot-plugging, page 139.
45 3 Configuring virtual machines
Enable 2D video acceleration If a virtual machine with Microsoft Windows has Guest Addi- tions installed, you can select here whether the guest should support accelerated 2D video graphics. Please refer to chapter 4.4.2, Hardware 2D video acceleration for Windows guests, page 66 for details.Remote display Under the “Remote display” tab, if the VirtualBox Remote Display Extension (VRDE) is installed, you can enable the VRDP server that is built into VirtualBox. This allows you to connect to the virtual machine remotely with any standard RDP viewer, such as mstsc.exe that comes with Microsoft Windows or, on Linux systems, the standard open- source rdesktop program. These features are described in detail in chapter 7.1, Remote display (VRDP support), page 91. 72.
If you have used the “Create VM” wizard to create a machine, you will normally see somethinglike the following:
Depending on the guest operating system type that you selected when you created the VM, thetypical layout of storage devices in a new VM is as follows:
• You will see an IDE controller, to which a virtual CD/DVD drive has been attached (to the “secondary master” port of the IDE controller).
46 3 Configuring virtual machines
•differ. You might then only have an IDE controller to which both the CD/DVD drive and the harddisks have been attached. This might also apply if you selected an older operating system typewhen you created the VM. Since older operating systems do not support SATA without additionaldrivers, VirtualBox will make sure that no such devices are present initially. Please see chapter5.1, Hard disk controllers: IDE, SATA (AHCI), SCSI, SAS, page 72 for additional information. VirtualBox also provides a floppy controller, which is special: you cannot add devices otherthan floppy drives to it. Virtual floppy drives, like virtual CD/DVD drives, can be connected toeither a host floppy drive (if you have one) or a disk image, which in this case must be in RAWformat. You can modify these media attachments freely. For example, if you wish to copy some filesfrom another virtual disk that you created, you can connect that disk as a second hard disk, as inthe above screenshot. You could also add a second virtual CD/DVD drive, or change where theseitems are attached. The following options are available:
• To add another virtual hard disk, or a CD/DVD or floppy drive, select the storage con- troller, offer- ing you to either select a virtual hard disk file using a standard file dialog or to create a new hard disk (image file), which will bring up the “Create new disk” wizard, which was described in chapter 1.7, Creating your first virtual machine, page 16. For details on the image file types that are supported, please see chapter 5.2, Disk image files (VDI, VMDK, VHD, HDD), page 74. –: ∗ 82. ∗ If you select “Remove disk from virtual drive”, VirtualBox will present an empty CD/DVD drive to the guest into which no media has been inserted.
47 3 Configuring virtual machines
• To remove an attachment, select it and click on the “remove” icon at the bottom (or right-click on it and select the menu item). Removable media (CD/DVDs and floppies) can be changed while the guest is running. Sincethe “Settings” dialog is not available at that time, you can also access these settings from the“Devices” menu of your virtual machine window.
48 3 Configuring virtual machines
You can use either the graphical user interface or the command-line VBoxManage tool to set upvirtual serial ports. For the latter, please refer to chapter 8.7, VBoxManage modifyvm, page 110;in that section, look for the --uart and --uartmode options. In either case, you can configure up to two virtual serial ports simultaneously. For each suchdevice, you will need to determine
1. what kind of serial port the virtual machine should see by selecting an I/O base address and interrupt (IRQ). For these, we recommend to use the traditional values8 ,: • You can elect to have the virtual serial port “disconnected”, which means that the guest will see the device, but it will behave as if no cable had been connected to it. •. • You can tell VirtualBox to connect the virtual serial port to a software pipe on the host. This depends on your host operating system: – On a Windows host, data will be sent and received through a named pipe. You can use a helper program called VMware Serial Line Gateway, available for down- load at. This tool provides a fixed server mode named pipe at \\.\pipe\vmwaredebug and connects incom- ing TCP connections on port 567 with the named pipe. – On a Mac, Linux or OpenSolaris host, a local domain socket is used instead..
Up to two serial ports can be configured simultaneously per virtual machine, but you can pickany port numbers out of the above. For example, you can configure two serial ports to be able towork with COM2 and COM4 in the guest.
49 3 Configuring virtual machines 178.
In addition to allowing a guest access to your local USB devices, VirtualBox even allows yourguests to connect to remote USB devices by use of the VirtualBox Remote Desktop Extension(VRDE). For details about this, see chapter 7.1.4, Remote USB, page 94. In the Settings dialog, you can first configure whether USB is available in the guest at all, andin addition also optionally enable the USB 2.0 (EHCI) controller for the guest. If so, you candetermine in detail which devices are available. For this, you must create so-called “filters” byspecifying certain properties of the USB device.
Note: The EHCI controller is shipped as a VirtualBox extension package, which must be installed separately. See chapter 1.5, Installing VirtualBox and extension packs, page 14 for more information.
Clicking on the “+“ button to the right of the “USB Device Filters” window creates a new filter.You can give the filter a name (for referencing it later) and specify the filter criteria. The morecriteria you specify, the more precisely devices will be selected. For instance, if you specify onlya vendor ID of 046d, all devices produced by Logitech will be available to the guest. If you fillin all fields, on the other hand, the filter will only apply to a particular device model from aparticular vendor, and not even to other devices of the same type with a different revision andserial 100):.
50 3 Configuring virtual machines
On a Windows host, you will need to unplug and reconnect a USB device to use it after creatinga filter for it. As an example, you could create a new USB filter and specify a vendor ID of 046d (Logitech,Inc), a manufacturer index of 1, and “not remote”. Then any USB devices on the host systemproduced filtername.
One notable user of EFI is Apple’s Mac OS X, but recent Linuxes (such as Fedora 11) and Windows(starting with Vista) offer special versions that can be booted using EFI as well. Another possible use of EFI in VirtualBox is development and testing of EFI applications, with-out booting any OS.
51 3 Configuring virtual machines
Note that the VirtualBox EFI support is experimental and will be enhanced as EFI matures andbecomes more widespread. While Mac OS X and Linux guests are known to work fine, Windowsguests are currently unable to boot with the VirtualBox EFI implementation.VBoxManage setextradata "VM name" VBoxInternal2/UgaVerticalResolution 900
The video mode for both GOP and UGA can only be changed when the VM is powered off andremains persistent until changed.
524 Guest AdditionsThe previous chapter covered getting started with VirtualBox and installing operating systems ina virtual machine. For any serious and interactive use, the VirtualBox Guest Additions will makeyour life much easier by providing closer integration between host and guest and improving theinteractive performance of guest systems. This chapter describes the Guest Additions in detail.
4.1 IntroductionAs mentioned in chapter 1.2, Some terminology, page 10, the Guest Additions are designed tobe installed inside a virtual machine after the guest operating system has been installed. Theyconsist of device drivers and system applications that optimize the guest operating system forbetter performance and usability. Please see chapter 3.1, Supported guest operating systems, page39 for details on what guest operating systems are fully supported with Guest Additions byVirtualBox. The VirtualBox Guest Additions for all supported guest operating systems are provided as asingle CD-ROM image file which is called VBoxGuestAdditions.iso. This image file is locatedin the installation directory of VirtualBox. To install the Guest Additions for a particular VM, youmount this ISO file in your VM as a virtual CD-ROM and install from there. The Guest Additions offer the following features:
Mouse pointer integration To overcome the limitations for mouse support that were described in chapter 1.8.2, Capturing and releasing keyboard and mouse, page 19, 63 au- tomatically adjusted (as if you had manually entered an arbitrary resolution in the guest’s display settings). Please see chapter 1.8.5, Resizing the machine’s window, page 21 also. Finally, if the Guest Additions are installed, 3D graphics and 2D video for guest applications can be accelerated; see chapter 4.4, Hardware-accelerated graphics, page 65.Seamless windows With this feature, the individual windows that are displayed on the desktop of the virtual machine can be mapped on the host’s desktop, as if the underlying application was actually running on the host. See chapter 4.5, Seamless windows, page 67 for details.
53.6, Guest properties, page 67 for details. Additionally, applications can be started in a guest from the host; see chapter 4.7, Guest control, page 69 9.11.3, Tuning the Guest Additions time synchronization parameters, page 148 for how to configure the parameters of the time synchronization mechanism.Shared clipboard With the Guest Additions installed, the clipboard of the guest operating sys- tem can optionally be shared with your host operating system; see chapter 3.3, General settings, page 42.Automated logons (credentials passing) For details, please see chapter 9.2, Automated guest logons, page 136.
Each version of VirtualBox, even minor releases, ship with their own version of the GuestAdditions. While the interfaces through which the VirtualBox core communicates with the GuestAdditions are kept stable so that Guest Additions already installed in a VM should continue towork when VirtualBox is upgraded on the host, for best results, it is recommended to keep theGuest Additions at the same version. Starting with VirtualBox 3.1, the Windows and Linux Guest Additions therefore check auto-matically whether they have to be updated. If the host is running a newer VirtualBox versionthan the Guest Additions, a notification with further instructions is displayed in the guest. To disable this update check for the Guest Additions of a given virtual machine, set the valueof its /VirtualBox/GuestAdd/CheckHostVersion guest property to 0; see chapter 4.6, Guestproperties, page 67 for details.
54 4 Guest Additions
4.2.1.1 InstallationIn the “Devices” menu in the virtual machine’s menu bar, VirtualBox has a handy menu itemnamed “Install guest additions”, which mounts the Guest Additions ISO file inside your virtualmachine. A Windows guest should then automatically start the Guest Additions installer, whichinstalls the Guest Additions into your Windows guest.
Note: For Direct 3D acceleration to work in a Windows Guest, you must install the Guest Additions in “Safe Mode”; see chapter 14, Known limitations, page 178 for de- tails.
If you prefer to mount the additions manually, you can perform the following steps:
3. In the Virtual Media Manager, press the “Add” button and browse your host file system for the VBoxGuestAdditions.iso file: • On a Windows host, you can find this file in the VirtualBox installation directory (usually under C:\Program files\Oracle/). •.
Unless you have the Autostart feature disabled in your Windows guest, Windows will nowautostart the VirtualBox Guest Additions installation program from the Additions ISO. If theAutostart feature has been turned off, choose VBoxWindowsAdditions.exe from the CD/DVDdrive inside the guest to start the installer. The installer will add several device drivers to the Windows driver database and then invokethe hardware detection wizard. Depending on your configuration, it might display warnings that the drivers are not digitallysigned. You must confirm these in order to continue the installation and properly install theAdditions. After installation, reboot your guest operating system to activate the Additions.
55 4 Guest Additions
For each, choose to provide your own driver and use “Have Disk” to point the wizard to theCD-ROM drive with the Guest Additions.
This automatically installs the right files and drivers for the corresponding platform (32- or64-bit).
Note: Because of the drivers are not yet WHQL certified, you still might get some driver installation popups, depending on the Windows guest version.
For more options regarding unattended guest installations, consult the command line help byusing the command:VBoxWindowsAdditions.exe /?
To explicitly extract the Windows Guest Additions for another platform than the current run-ning one (e.g. 64-bit files on a 32-bit system), you have to execute the appropriate platforminstaller (VBoxWindowsAdditions-x86.exe or VBoxWindowsAdditions-amd64.exe) with the/extract parameter.
56 4 Guest Additions
Make sure to nstall DKMS before installing the Linux Guest Additions. 2. Mount the VBoxGuestAdditions.iso file as your Linux guest’s virtual CD-ROM drive, exactly the same way as described for a Windows guest in chapter 4.2.1.1, Installation, page 55. 3. Change to the directory where your CD-ROM drive is mounted and execute as root: sh ./VBoxLinuxAdditions-x86.run
57 4 Guest Additions
1. In order to update your system to the latest version of the packets, open a terminal and as root, execute apt-get update
followed by apt-get upgrade
3. Reboot your guest system in order to activate the updates and then proceed as described above.
Fedora 13 (“Goddard”) 1. In order to update your system to the latest version of the packets, open a terminal and as root, execute yum update
followed by yum install gcc
openSUSE 11.2 1. In order to update your system to the latest version of the packets, open a terminal and as root, execute zypper update
5. Make sure that your running kernel (uname -a) and the kernel packages you have installed (rpm -qa kernel\*) have the exact same version number. Proceed with the installation as described above.
58 4 Guest Additions
Mandrake 2010 1. Mandrake ships with the VirtualBox Guest Additions which will be replaced if you follow these steps. 2. In order to update your system to the latest version of the packets, open a terminal and as root and execute urpmi --auto-update
and make sure to choose the correct kernel-devel package when asked by the installer (use uname -a to compare).
CentOS 5.5, Red Hat Enterprise Linux 5.5 and Oracle Enterprise Linux 5.5 1.. In case Oracle Enterprise Linux does not find the required packages, you either have to install them from a different source (e.g. DVD) or use Oracle’s public Yum server located at.
59 4 Guest Additions
Debian 5 (“Lenny”)
4. Determine the exact version of your kernel using uname -a and install the correct version of the linux-headers package, e.g. using apt-get install linux-headers-2.6.26-2-686
Note that OpenGL support is not available unless you update to a later Linux kernel.
as root (you will need to replace lib by lib64 on some 64bit guests), and on older guests withoutthe udev service you will need to add the vboxadd service to the default runlevel to ensure thatthe modules get loaded. To setup the time synchronization service, run the command /usr/lib/VBoxGuestAdditions/vboxadd-service setup
and add the service vboxadd-service to the default runlevel. To set up the X11 and OpenGLpart of the Guest Additions, run the command /usr/lib/VBoxGuestAdditions/vboxadd-x11 setup
After compilation you should reboot your guest to ensure that the new modules are actuallyused.
60 4 Guest Additions
With a 64-bit guest, use VBoxLinuxAdditions-amd64 instead. While this will normally workwithout issues, you may need to do some manual cleanup of the guest (particularly of theXFree86Config or xorg.conf file) in some cases, particularly if the Additions version installedor the guest operating system were very old, or if you made your own changes to the GuestAdditions setup after you installed them. Starting with version 3.1.0, you can uninstall the Additions by invoking/opt/VBoxGuestAdditions-4.0.0/uninstall.sh
61 4 Guest Additions
• Solaris 11 Express; • Solaris 10 (u5 and higher); • Solaris Nevada/SXDE/SXCE (build 82 and higher);
• OpenSolaris (Developer Preview 2 and higher; this includes OpenSolaris 2008.05, 2008.11 and 2009.06);
Other distributions may work if they are based on comparable software releases.
1. Mount the VBoxGuestAdditions.iso file as your Solaris guest’s virtual CD-ROM drive, exactly the same way as described for a Windows guest in chapter 4.2.1.1, Installation, page 55..
62 4 Guest Additions
• In the window of a running VM, you can select “Shared folders” from the “Devices” menu, or click on the folder icon on the status bar in the bottom right corner. • If a VM is not currently running, you can configure shared folders in each virtual machine’s “Settings” dialog.
• From the command line, you can create shared folders using VBoxManage, as follows: VBoxManage sharedfolder add "VM name" --name "sharename" --hostpath "C:\test"
See chapter 8.27, VBoxManage sharedfolder add/remove, page 127 for details.guest to have read-only access, create a read-only shared folder. This can either be achievedusing the GUI or by appending the parameter --readonly when creating the shared folder withVBoxManage. Starting with version 4.0, VirtualBox shared folders also support symbolic links (symlinks),under the following conditions:
1. The host operating system must support symlinks (i.e. a Mac, Linux or Solaris host is required).
63 4 Guest Additions
• In a Windows guest, shared folders are browseable and therefore visible in Windows Ex- plorer. So, to attach the host’s shared folder to your Windows guest, open Windows Ex- plorer.
To mount a shared folder during boot, add the following entry to /etc/fstab: sharename mountpoint vboxsf defaults 0 0). The generic mount options (documented in the mount manual page) apply also. Espe- cially useful are the options uid, gid and mode, as they allow access by normal users (in read/write mode, depending on the settings) even if root has mounted the filesystem.
64 4 Guest Additions
• With Windows guests, any auto-mounted shared folder will receive its own drive letter (e.g. E:) depending on the free drive letters remaining in the guest. If there no free drive letters left, auto-mounting will fail; as a result, the number of auto- mounted shared folders is typically limited to 22 or less with Windows guests.
•.6, Guest properties, page 67.
To change the mount directory to something other than /media, you can set the guest property /VirtualBox/GuestAdd/SharedFolders/MountDir. • Solaris guests behave like Linux guests except that /mnt is used as the default mount directory instead of /media.
To have any changes to auto-mounted shared folders applied while a VM is running, the guestOS needs to be rebooted. (This applies only to auto-mounted shared folders, not the ones whichare mounted manually.)
1. It is only available for certain Windows, Linux and Solaris guests. In particular:.
65 4 Guest Additions
• 3D acceleration with Windows guests requires Windows 2000, Windows XP, Vista or Windows 7. Both OpenGL and Direct3D 8/9 (not with Windows 2000) are supported (experimental). • OpenGL on Linux requires kernel 2.6.27 and higher as well as X.org server version 1.5 and higher. Ubuntu 10.10 and Fedora 14 have been tested and confirmed as working. • OpenGL on Solaris guests requires X.org server version 1.5 and higher. 2. The Guest Additions must be installed.
3. Because 3D support is still experimental at this time, it is disabled by default and must be manually enabled in the VM settings (see chapter 3.3, General settings, page 42).
66 4 Guest Additions
After seamless windows are enabled (see below), VirtualBox suppresses the display of theDesktop background of your guest, allowing you to run the windows of your guest operatingsystem seamlessly next to the windows of your host:
To enable seamless mode, after starting the virtual machine, press the Host key (normally theright control key) together with “L”. This will enlarge the size of the VM’s display to the sizeof your host screen and mask out the guest operating system’s background. To go back to the“normal” VM display (i.e. to disable seamless windows), press the Host key and “L” again.
2 TheX server version is not the same as the version of the entire X.org suite. You can type X -version in a terminal to find out about the X.org server version level that is currently installed.
67 4 Guest Additions
2. In addition, arbitrary string data can be exchanged between guest and host. This works in both directions.
68 4 Guest Additions
To query the value of a single property, use the “get” subcommand like this:$ VBoxManage guestproperty get "Windows Vista III" "/VirtualBox/GuestInfo/OS/Product"VirtualBox Command Line Management Interface Version 4.0.0(C) 2005-2010 Oracle CorporationAll rights reserved.
To add or change guest properties from the guest, use the tool VBoxControl. This tool isincluded in the Guest Additions of VirtualBox 2.2 or later. When started from a Linux guest, thistool requires root privileges for security reasons:$ sudo VBoxControl guestproperty enumerateVirtualBox Guest Additions Command Line Management Interface Version 4.0.0(C) 2009-2010 Oracle CorporationAll rights reserved.
For more complex needs, you can use the VirtualBox programming interfaces; see chapter 11,VirtualBox programming interfaces, page 161.
69 4 Guest Additions
Note: VirtualBox supports memory ballooning only on 64-bit hosts, and it is not sup- ported on Mac OS X hosts.
Normally, to change the amount of memory allocated to a virtual machine, one has to shutdown the virtual machine entirely and modify its settings. With memory ballooning, memorythat was allocated for a virtual machine can be given to another virtual machine without havingto shut the machine down. When memory ballooning is requested, the VirtualBox Guest Additions (which run inside theguest) allocate physical memory from the guest operating system on the kernel level and lockthis memory down in the guest. This ensures that the guest will not use that memory any longer:no guest applications can allocate it, and the guest kernel will not use it either. VirtualBox canthen re-use this memory and give it to another virtual machine. The memory made available through the ballooning mechanism is only available for re-use byVirtualBox. It is not returned as free memory to the host. Requesting balloon memory from arunning guest will therefore not increase the amount of free, unallocated memory on the host.Effectively, memory ballooning is therefore a memory overcommitment mechanism for multiplevirtual machines while they are running. This can be useful to temporarily start another machine,or in more complicated environments, for sophisticated memory management of many virtualmachines that may be running in parallel depending on how memory is used by the guests. At this time, memory ballooning is only supported through VBoxManage. Use the follow-ing command to increase or decrease the size of the memory balloon within a running virtualmachine that has Guest Additions installed:VBoxManage controlvm "VM name" guestmemoryballoon <n>
where "VM name" is the name or UUID of the virtual machine in question and <n> is the amountof memory to allocate from the guest in megabytes. See chapter 8.11, VBoxManage controlvm,page 118 for more information. You can also set a default balloon that will automatically be requested from the VM every timeafter.7, VBoxManagemodifyvm, page 110.
70 4 Guest Additions
In a server environment running several similar VMs (e.g. with identical operating systems)on the same host, lots of memory pages are identical. VirtualBox’s Page Fusion technology,introduced with VirtualBox 3.2, is a novel technique to efficiently identify these identical memorypagesamount of host memory that is in use. It therefore works best if all VMs on a host run identicaloperating systems (e.g. Windows XP Service Pack 2). Instead of having a complete copy of eachoperating system in each VM, Page Fusion identifies the identical memory pages in use by theseoperating systems and eliminates the duplicates, sharing host memory between several machines(“deduplication”). If a VM tries to modify a page that has been shared with other VMs, a newpage is allocated again for that VM with a copy of the shared page (“copy on write”). All this isfully transparent to the virtual machine. You may be familiar with this kind of memory overcommitment from other hypervisor prod-ucts, which call this feature “page sharing” or “same page merging”. However, Page Fusion differssignificantly from those other solutions, whose approaches have several drawbacks: isshut down. To enable Page Fusion for a VM, use the following command:VBoxManage modifyvm "VM name" --pagefusion on
You can observe Page Fusion operation using some metrics. RAM/VMM/Shared shows the totalamount of fused pages, whereas the per-VM metric Guest/RAM/Usage/Shared will return theamount of fused memory for a given VM. Please refer to chapter 8.31, VBoxManage metrics, page131 for information on how to query metrics.
715 Virtual storageAs 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 arepresently 74. 2. Alternatively, if you have iSCSI storage servers, you can attach such a server to VirtualBox as well; this is described in chapter 5.10, iSCSI servers, page 83.
3. Finally, as an experimental feature, you can allow a virtual machine to access one of your host disks directly; this advanced feature is described in chapter 9.6.1, Using a raw host hard disk from a guest, page 140.
Each such virtual storage device (image file, iSCSI target or physical hard disk) will need to beconnected to the virtual hard disk controller that VirtualBox presents to a virtual machine. Thisis explained in the next section.
• IDE (ATA) controllers have been in use since the 1980s. Initially, this type hard disk controllers have two connectors for such cables; as a result, most PCs support up to four devices. In VirtualBox, each virtual machine has one IDE controller enabled by default, the default IDE controller that is enabled by default. You can also select which exact type of IDE controller hardware VirtualBox should present to the virtual machine (PIIX3, PIIX4 or ICH6). This makes no difference in terms of per- formance, but if you import a virtual machine from another virtualization product, the.2 The assignment of the machine’s CD/DVD drive to the secondary master was fixed before VirtualBox 3.1; it is now
changeable, and the drive can be at other slots of the IDE controller, and there can be more than one such drive.
72 5 Virtual storage
operating system in that machine may expect a particular controller.• Serial ATA (SATA) is a newer standard introduced in 2003. con- nect up to 30 virtual hard disks to one machine instead of just three, as with the VirtualBox IDE controller (with the DVD drive already attached). Of these, the first four (numbered 0-3 in the graphical user interface) are operated in IDE compatibility mode by default. http:// downloadcenter.intel.com/Product_Filter.aspx?ProductID=2101.
To add a SATA controller to a machine for which it has not been enabled by default (either because it was created by an earlier version of VirtualBox, or because SATA is not sup- ported.17, VBoxManage storagectl, page 122.• SCSI is another established industry standard, standing for “Small Computer System In- terface”. SCSI was standardized as early as 1986 as a generic interface for data transfer between all kinds of devices, including storage devices. Today SCSI is still used for connect- ing hard disks and tape devices, but it has mostly been displaced in commodity hardware. It is still in common use in high-performance workstations and servers. Primarily for compatibility with other virtualization software, VirtualBox optionally sup- ports LSI Logic and BusLogic SCSI controllers, to each of which up to 15 virtual hard disks can be attached.
73 5 Virtual storage
To enable a SCSI controller, on the “Storage” page of a virtual machine’s settings dialog, click on the “Add Controller” button under the “Storage Tree” box and then select “Add.
•2) will not see such disks unless you install additional drivers.
In summary, VirtualBox gives you the following categories of virtual storage slots:
1. four slots attached to the traditional IDE controller, which are always present (one of which typically is a virtual CD/DVD drive);
2. 30 slots attached to the SATA controller, if enabled and provided that your guest operating system can see it; these slots can either be a) in IDE compatibility mode (by default, slots 0-3) or b) in SATA mode;
3. 15 slots attached to the SCSI controller, if enabled and supported by the guest operating system; 4. eight slots attached to the SAS controller, if enabled and supported by the guest operating system.
Given this large choice of storage controllers, you may ask yourself which one to choose. Ingeneral, you should avoid IDE unless it is the only controller supported by your guest. Whetheryou use SATA, SCSI or SAS does not make any real difference. The variety of controllers is onlysupplied for VirtualBox for compatibility with existing hardware and other hypervisors.
74 5 Virtual storage
Like a physical disk, a virtual disk has a size (capacity), which must be specified when theimage file is created. As opposed to a physical disk however, VirtualBox allows you to expandan image file after creation, even if it has data already; see chapter 8.21, VBoxManage modifyhd,page 124 for details.3 VirtualBox supports four variants of disk image files:
• Normally, VirtualBox uses its own container format for guest hard disks – Virtual Disk Image (VDI) files. In particular, this format will be used when you create a new virtual machine with a new disk. • VirtualBox also fully supports the popular and open VMDK container format that is used by many other virtualization products, in particular, by VMware.4 • VirtualBox also fully supports the VHD format used by Microsoft. • Image files of Parallels version 2 (HDD format) are also supported.5 For lack of documen- tation of the format, newer formats (3 and 4) are not supported. You can however convert such image files to version 2 format using tools provided by Parallels.
Irrespective of the disk capacity and format, as briefly mentioned in chapter 1.7, Creating yourfirst virtual machine, page 16, there are two options of how to create a disk image: fixed-size ordynamically expanding.
•. •.
The known media can be viewed and changed in the Virtual Media Manager, which you canaccess from the “File” menu in the VirtualBox main window:
75 5 Virtual storage
The known media are conveniently grouped in three tabs for the three possible formats. Theseformats are: • Hard disk images, either in VirtualBox’s own Virtual Disk Image (VDI) format or in the third-party formats listed in the previous chapter; • CD/DVD images in standard ISO format; • floppy images in standard RAW format. As you can see in the screenshot above, for each image, the Virtual Media Manager shows youthe full path of the image file and other information, such as the virtual machine the image iscurrently attached to, if any. The Virtual Media Manager allows you to • remove an image from the registry (and optionally delete the image file 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. Starting with version 4.0, to create new disk images, please use the “Storage” page in a virtualmachine’s settings dialog because disk images are now by default stored in each machine’s ownfolder. Hard disk image files can be copied onto other host systems and imported into virtual machinesthere, although certain guest systems (notably Windows 2000 and XP) will require that the newvirtual 80 for instructions on this matter. Also, if you want to copy a virtual machine to another system, VirtualBox has an import/export facility that might be better suited for your needs; see chapter 1.12, Importing and exporting virtual machines, page 26.
76 5 Virtual storage
Warning: This is an expert feature, and misuse can lead to data loss – regular filesys- tems are not prepared to handle simultaneous changes by several parties.
4. Next, immutable images only remember write accesses temporarily while the virtual ma- chine- up, those images are reset to the state of the last (current) snapshot (instead of the state of the original immutable image).6 This restriction is more lenient now than it was before VirtualBox 2.2. Previously, each “normal” disk image could only be attached to one single machine. Now it can be attached to more than one machine so long as only one of these machines is running.
77 5 Virtual storage pre- viously. To re-enable the automatic resetting of such images, delete the current snap- shot im- mutable.21, VBoxManage modifyhd, page 124.
6. Finally, the read-only image is used automatically for CD/DVD images, since CDs/DVDs can never be written to.
To illustrate the differences between the various types with respect to snapshots: Assumeyou have installed your guest operating system in your VM, and you have taken a snapshot.Imagine you have accidentally infected your VM with a virus and would like to go back to thesnapshot. With a normal hard disk image, you simply restore the snapshot, and the earlierstate of your hard disk image will be restored as well (and your virus infection will be undone).With an immutable hard disk, all it takes is to shut down and power on your VM, and the virusinfection will be discarded. With a write-through image however, you cannot easily undo thevirus infection by means of virtualization, but will have to disinfect your virtual machine like areal computer. Still, you might find write-through images useful if you want to preserve critical data irrespec-tive of snapshots, and since you can attach more than one image to a VM, you may want to haveone immutable for the operating system and one write-through for your data files.
78 5 Virtual storage
When a differencing image is active, it receives all write operations from the virtual machineinstead of its parent. The differencing image only contains the sectors of the virtual hard diskthat have changed since the differencing image was created. When the machine reads a sectorfrom such a virtual hard disk, it looks into the differencing image first. If the sector is present,it is returned from there; if not, VirtualBox looks into the parent. In other words, the parentbecomes “read-only”; it is never written to again, but it is read from if a sector has not changed. Differencing images can be chained. If another differencing image is created for a virtual diskthat already has a differencing image, then it becomes a “grandchild” of the original parent.The first differencing image then becomes read-only as well, and write operations only go to thesecond-level differencing image. When reading from the virtual disk, VirtualBox needs to lookinto the second differencing image first, then into the first if the sector was not found, and theninto the original image. There can be an unlimited number of differencing images, and each image can have more thanone child. As a result, the differencing images can form a complex tree with parents, “siblings”and children, depending on how complex your machine configuration is. Write operations alwaysgo:
In all of these situations, from the point of view of the virtual machine, the virtual hard diskbehaves like any other disk. While the virtual machine is running, there is a slight run-time I/Ooverhead because VirtualBox might need to look up sectors several times. This is not noticeablehowever since the tables with sector information are always kept in memory and can be lookedup.
79 5 Virtual storage.
80cache to buffer writes, but no read caching since this is typically already performed by the guestOS. In addition, VirtualBox fully supports asynchronous I/O for its virtual SATA, SCSI and SAScontrollers through multiple I/O threads. Since asynchronous I/O is not supported by IDE controllers, for performance reasons, you maywant to leave host caching enabled for your VM’s virtual IDE controllers. For this reason, VirtualBox allows you to configure whether the host I/O cache is used for eachI/O controller separately. Either uncheck the “Use host I/O cache” box in the “Storage” settingsfor a given virtual storage controller, or use the following VBoxManage command to disable thehost I/O cache for a virtual storage controller:VBoxManage storagectl <vm> --name <controllername> --hostiocache off
81 5 Virtual storage
Limits are configured through VBoxManage. The example below creates a bandwidth groupnamed “Limit”, sets the limit to 20 MB/s and assigns the group to the attached disks of the VM:VBoxManage bandwidthctl "VM name" --name Limit --add disk --limit 20VBoxManage storageattach "VM name" --controller "SATA" --port 0 --device 0 --type hdd --medium disk1.vdi --bandwidthgroup LimitVBoxManage storageattach "VM name" --controller "SATA" --port 1 --device 0 --type hdd --medium disk2.vdi --bandwidthgroup Limit
All disks in a group share the bandwidth limit, meaning that in the example above the band-width of both images combined can never exceed 20 MB/s. However if one disk doesn’t requirebandwidth the other can use the remaining bandwidth of its group. The limits for each group can be changed while the VM is running, with changes being pickedup immediately. The example below changes the limit for the group created in the exampleabove to 10 MB/s:VBoxManage bandwidthctl "VM name" --name Limit --limit 10
• Host Drive defines that the guest can read from the medium in the host drive. • Image file (typically an ISO file) gives the guest read-only access to the data in the image. • Empty stands for a drive without an inserted medium.
Changing between the above, or changing a medium in the host drive that is accessed by amachine, or changing an image file will signal a medium change to the guest operating system,which can then react to the change (e.g. by starting an installation program). Medium changes can be prevented by the guest, and VirtualBox reflects that by locking thehost drive if appropriate. You can force a medium removal in such situations via the VirtualBoxGUI or the VBoxManage command line tool. Effectively this is the equivalent of the emergencyeject which many CD/DVD drives provide, with all associated side effects: the guest OS can issueerror messages, just like on real hardware, and guest applications may misbehave. Use this withcaution. sys- tem every time the configuration is changed.
The standard CD/DVD emulation allows for reading standard data CD and DVD formats only.As an experimental feature, for additional capabilities, it is possible to give the guest direct accessto the CD/DVD host drive by enabling “passthrough” mode. Depending on the host hardware,this may enable three things to work, potentially:
• CD/DVD writing from within the guest, if the host DVD drive is a CD/DVD writer; • playing audio CDs; • playing encrypted DVDs.
82 5 Virtual storage
There is a “Passthrough” checkbox in the GUI dialog for configuring the media attached to astorage controller, or you can use the --passthrough option with VBoxManage storageattach;see chapter 8.16, VBoxManage storageattach, page 120 for details. Even if pass-through is enabled, unsafe commands, such as updating the drive firmware, willbe blocked. Video CD formats are never supported, not even in passthrough mode, and cannotbe played from a virtual machine. On Solaris hosts, pass-through requires running VirtualBox with real root permissions due tosecurity measures enforced by the host.
836 Virtual networkingAs briefly mentioned in chapter 3.8, Network settings, page 48, VirtualBox provides up to eightvirtual PCI Ethernet cards for each virtual machine. For each such card, you can individuallyselect
2. the virtualization mode that the virtual card will be operating in with respect to your physical networking hardware on the host.
Four of the network cards can be configured in the “Network” section of the settings dialogin the graphical user interface of VirtualBox. You can configure all eight network cards on thecommand line via VBoxManage modifyvm; see chapter 8.7, VBoxManage modifyvm, page 110. This chapter explains the various networking settings in more detail.
The PCNet FAST III is the default because it is supported by nearly all operating systems outof the box, as well as the GNU GRUB boot manager. As an exception, the Intel PRO/1000 familyadapters are chosen for some guest operating system types that no longer ship with drivers forthe PCNet card, such as Windows Vista; see chapter 4.2.1.5, Windows Vista networking, page 56for details.1 The “Paravirtualized network adapter (virtio-net)“ is special. If you select this, thenVirtualBox does not virtualize common networking hardware (that is supported by commonguest operating systems out of the box). Instead, VirtualBox then expects a special softwareinterface for virtualized environments to be provided by the guest, thus avoiding the complexityof emulating networking hardware and improving network performance. Starting with version3.1, VirtualBox provides support for the industry-standard “virtio” networking drivers, which arepart 1.6.2 because this one is recognized by Windows XP guests without additional driver installation. The MT Server variant was added with VirtualBox 2.2 to facilitate OVF imports from other platforms.
84 6 Virtual networking
• Linux kernels version 2.6.25 or later can be configured to provide virtio support; some distributions also back-ported virtio to older kernels.
• For Windows 2000, XP and Vista, virtio drivers can be downloaded and installed from the KVM project web page.2
VirtualBox also has limited support for so-called jumbo frames, i.e. networking packets withmore than 1500 bytes of data, provided that you use the Intel card virtualization and bridgednetworking. In other words, jumbo frames are not supported with the AMD networking devices;in those cases, jumbo packets will silently be dropped for both the transmit and the receivedirection. Guest operating systems trying to use this feature will observe this as a packet loss,which may lead to unexpected application behavior in the guest. This does not cause problemswith guest operating systems in their default configuration, as jumbo frames need to be explicitlyenabled. e-mail inside the guest, then this default mode should be sufficient for you, and you can safely skip the rest of this section. Please note that there are certain limitations when using Windows file sharing (see chapter 6.3.3, NAT limitations, page 87.
2.
85 6 Virtual networking
With the above example, all TCP traffic arriving on port 2222 on any host interface will beforwarded to port 22 in the guest. The protocol name tcp is a mandatory attribute definingwhich protocol should be used for forwarding (udp could also be used). The name guestssh ispurely descriptive and will be auto-generated if omitted. The number after --natpf denotes thenetwork card, like in other parts of VBoxManage. To remove this forwarding rule again, use the following command:
86 6 Virtual networking
If for some reason the guest uses a static assigned IP address not leased from the built-in DHCPserver,guest can be found at the 10.0.2.19 address. To forward all incoming traffic from a specific host interface to the guest, specify the IP of thathost interface like this:VBoxManage modifyvm "VM name" --natpf1 "guestssh,tcp,127.0.0.1,2222,,22"
This forwards all TCP traffic arriving on the localhost interface (127.0.0.1) via port 2222 to port22 in the guest. It is not possible to configure incoming NAT connections while the VM is running. However,you can change the settings for a VM which is currently saved (or powered off at a snapshot).
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 sup- port sup- ported.also subtle effects that may interfere with protocols that are normally working. One example isNFS, where the server is often configured to refuse connections from non-privileged ports (i.e.ports not below 1024).
87 6 Virtual networkingmachine, go to the “Network” page and select “Bridged network” in the drop down list for the“Attached to” field. Finally, select desired host interface from the list at the bottom of the page,which contains the physical network interfaces of your systems. On a typical MacBook, forexample, this will allow you to select between “en1: AirPort” (which is the wireless interface)and “en0: Ethernet”, which represents the interface with a network cable. Depending on your host operating system, the following limitations should be kept in mind:
• On Macintosh hosts, functionality is limited when using AirPort (the Mac’s wireless net- working) for bridged networking. Currently, VirtualBox supports only IPv4 over AirPort. For other protocols such as IPv6 and IPX, you must choose a wired interface. • On Linux hosts, functionality is limited when using wireless interfaces for bridged net- working.. • On Solaris hosts, iden- tical MAC addresses.3 ForMac.
88 6 Virtual networking
When using VLAN interfaces with VirtualBox, they must be named according to the PPA- hack naming scheme (e.g. “e1000g513001”), as otherwise the guest may receive packets in an unexpected format.
•. • You can use VBoxManage modifyvm "VM name" --nic<x> intnet
If you do not specify a network name, the network card will be attached to the network intnet by default.
Unless you configure the (virtual) network cards in the guest operating systems that are partic-ipating in the internal network to use static IP addresses, you may want to use the DHCP serverthat is built into VirtualBox to manage IP addresses for the internal network. Please see chapter8.33, VBoxManage dhcpserver, page 132 for details. As a security measure, the Linux implementation of internal networking only allows VMsrunning under the same user ID to establish an internal network.
89 6 Virtual networking
Instead, when host-only networking is used, VirtualBox creates a new software interface onthe host which then appears next to your existing network interfaces. In other words, whereaswith bridged networking an existing physical interface is used to attach virtual machines to,with host-only networking a new “loopback” interface is created on the host. And whereas withinternal networking, the traffic between the virtual machines cannot be seen, the traffic on the“loopback” interface on the host can be intercepted. Host-only networking is particularly useful for preconfigured virtual appliances, where multi-ple virtual machines are shipped together and designed to cooperate. For example, one virtualmachine may contain a web server and a second one a database, and since they are intendedto talk to each other, the appliance can instruct VirtualBox to set up a host-only network for thetwo. A second (bridged) network would then connect the web server to the outside world toserve data to, but the outside world cannot connect to the database. To change a virtual machine’s virtual network interface to “host only” mode:
• either go to the “Network” page in the virtual machine’s settings notebook in the graphical user interface and select “Host-only networking”, or
• on the command line, type VBoxManage modifyvm "VM name" --nic<x> hostonly; see chapter 8.7, VBoxManage modifyvm, page 110 for details.
For host-only networking, like with internal networking, you may find the DHCP server usefulthat is built into VirtualBox. This can be enabled to then manage the IP addresses in the host-onlynetwork since otherwise you would need to configure all IP addresses statically.
•.
• Alternatively, you can use VBoxManage dhcpserver on the command line; please see chap- ter 8.33, VBoxManage dhcpserver, page 132 for details.
907 Remote virtual machines7.1 Remote display (VRDP support)VirtualBox can display virtual machines remotely, meaning that a virtual machine can executeon one machine even though the machine will be displayed on a second computer, and themachine will be controlled from there as well, as if the virtual machine was running on thatsecond computer. For maximum flexibility, starting with VirtualBox 4.0, VirtualBox implements remote machinedisplay through a generic extension interface, the VirtualBox Remote Desktop Extension (VRDE).The base open-source VirtualBox package only provides this interface, while implementationscan be supplied by third parties with VirtualBox extension packages, which must be installedseparately from the base package. See chapter 1.5, Installing VirtualBox and extension packs,page 14 for more information. Oracle provides support for the VirtualBox Remote Display Protocol (VRDP) in such aVirtualBox extension package. When this package is installed, VirtualBox versions 4.0 and latersupport VRDP the same way as binary (non-open-source) versions of VirtualBox before 4.0 did. VRDP is a backwards-compatible extension to Microsoft’s Remote Desktop Protocol (RDP).Typically graphics updates and audio are sent from the remote machine to the client, whilekeyboard and mouse events are sent back. As a result, you can use any standard RDP client tocontrol the remote VM. Even when the extension is installed, the VRDP server is disabled by default. It can easily beenabled on a per-VM basis either in the VirtualBox Manager in the “Display” settings (see chapter3.5, Display settings, page 45) or with VBoxManage:VBoxManage modifyvm "VM name" --vrde on
If you use VBoxHeadless (described further below), VRDP support will be automatically en-abled since VBoxHeadless has no other means of output.
91 7 Remote virtual machines
The actual port used by a running VM can be either queried with VBoxManage showvminfocommand or seen in the GUI on the “Runtime” tab of the “Session Information Dialog”, which isaccessible via the “Machine” menu of the VM window. Here follow examples for the most common RDP viewers:
• 1.2.3.4[:3389]
Replace “1.2.3.4” with the host IP address, and 3389 with a different port if necessary.
Note: When connecting to localhost in order to test the connection, the addresses localhost and 127.0.0.1 might not work using mstsc.exe. Instead, the address 127.0.0.2[:3389] has to be used.
• On other systems, you can use the standard open-source rdesktop program. This ships with most Linux distributions, but VirtualBox also comes with a modified variant of rdesk- top for remote USB support (see chapter 7.1.4, Remote USB, page 94 below). With rdesktop, use a command line such as the following: rdesktop -a 16 -N 1.2.3.4:3389
As said for the Microsoft viewer above, replace “1.2.3.4”. • If you run the KDE desktop, you might prefer krdc, the KDE RDP viewer. The command line would look like this: krdc --window --high-quality rdp:/1.2.3.4[:3389]
Again, replace “1.2.3.4” with the host IP address, and 3389 with a different port if neces- sary. The “rdp:/“ bit is required with krdc to switch it into RDP mode.
1 Before VirtualBox 1.6, the headless server was called VBoxVRDP. For the sake of backwards compatibility, the VirtualBox installation still installs an executable with that name as well.
92 7 Remote virtual machines
The extra --type option causes VirtualBox to use VBoxHeadless as the front-end to the internal virtualization engine instead of the Qt front-end.
This way of starting the VM is preferred becausemeans of output, the VRDP server will always be enabled, regardless of whether you had enabledthe VRDP server in the VM’s settings. If this is undesirable (for example because you want toaccess the VM via ssh only), start the VM like this:VBoxHeadless --startvm <uuid|name> --vrde=off
To have the VRDP server enabled depending on the VM configuration, as the other front-endswould, use this:VBoxHeadless --startvm <uuid|name> --vrde=config
1. VirtualBox on a server machine with a supported host operating system. The VirtualBox extension pack for the VRDP server must be installed (see the previous section). For the following example, we will assume a Linux server.
2. An ISO file accessible from the server, containing the installation data for the guest operat- 91 above for examples.
Note again that on the server machine, since we will only use the headless server, neither Qt norSDL nor the X Window system will be needed.
93 7 Remote virtual machines
If everything worked, you should see a copyright notice. If, instead, you are returned to the command line, then something went wrong. 8. On the client machine, fire up the RDP viewer and try to connect to the server (see chapter 7.1.1, Common third-party RDP viewers, page 91 above for how to use various common RDP viewers). You should now be seeing the installation routine of your guest operating system remotely in the RDP viewer.
Note that rdesktop-vrdp can access USB devices only through /proc/bus/usb. Please referto chapter 12.6.7, USB not working, page 174 for further details on how to properly set up thepermissions. Furthermore it is advisable to disable automatic loading of any host driver on theremote host which might work on USB devices to ensure that the devices are accessible by theRDP client. If the setup was properly done on the remote host, plug/unplug events are visible onthe VBox.log file of the VM.
94 7 Remote virtual machines
• The “null” method means that there is no authentication at all; any client can connect to the VRDP server and thus the virtual machine. This is, of course, very insecure and only to be recommended for private networks. •Lo- gon system. – On Mac OS X hosts, VBoxAuth.dylib authenticates users against the host’s di- rectory service.2 In other words, the “external” method per default performs authentication with the user accounts that exist on the host system. Any user with valid authentication creden- tials is accepted, i.e. the username does not have to correspond to the user running the VM. 2. An additional library called VBoxAuthSimple performs authentication against creden- tials
95 7 Remote virtual machines
• Finally, the “guest” authentication method performs authentication with a special compo- nent that comes with the Guest Additions; as a result, authentication is not performed on the host, but with the guest user accounts. This method is currently still in testing and not yet supported.
In addition to the methods described above, you can replace the default “external” authenti-cation module with any other module. For this, VirtualBox provides a well-defined interface thatallows you to write your own authentication module. This is described in detail in the VirtualBoxSoftware Development Kit (SDK) reference; please see chapter 11, VirtualBox programming in-terfaces, page 161 for details.
1. Historically, RDP4 authentication was used, with which the RDP client does not perform any checks in order to verify the identity of the server it connects to. Since user creden- tials. How- ever,environments where security is a concern. As the client that connects to the server determineswhat type of encryption will be used, with rdesktop, the Linux RDP viewer, use the -4 or -5options.
96 7 Remote virtual machines
number as the screen index. The primary guest screen is selected with @1, the first secondaryscreen is @2, etc. The Microsoft RDP6 client does not let you specify a separate domain name. Instead, usedomain\username in the Username: field – for example, @2\name. name must be supplied, andmust be the name used to log in if the VRDP server is set up to require credentials. If it is not,you may use any text as the username.
The quality of the video is defined as a value from 10 to 100 percent, representing a JPEGcompression level (where lower numbers mean lower quality but higher compression). Thequality can be changed using the following command:VBoxManage modifyvm "VM name" --vrdevideochannelquality 75
To reenable a feature use a similar command without the trailing 1. For example:VBoxManage modifyvm "VM name" --vrdeproperty Client/DisableDisplay=
These properties were introduced with VirtualBox 3.2.10. However, in the 3.2.x series, it wasnecessary to use the following commands to alter these settings instead:VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableDisplay" 1VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableInput" 1VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableUSB" 1VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableAudio" 1V"
97 7 Remote virtual machines
7.2 TeleportingStarting with version 3.1, VirtualBox supports “teleporting” – that is, moving a virtual machineover a network from one VirtualBox host to another, while the virtual machine is running. Thisworks regardless of the host operating system that is running on the hosts: you can teleportvirtual machines between Solaris and Mac hosts, for example. Teleporting requires that a machine be currently running on one host, which is then calledthe  minimaldowntime. Teleporting happens over any TCP/IP network; the source and the target only need to agree 6000. For details, see chapter 8.7.5, Teleporting settings, page 115.
2..11, VBoxManage controlvm, page 118.
For testing, you can also teleport machines on the same host; in that case, use “localhost” asthe hostname on both the source and the target host.
98 7 Remote virtual machines
Note: In rare cases, if the CPUs of the source and the target are very different, tele-porting can fail with an error message, or the target may hang. This may happenespecially if the VM is running application software that is highly optimized to runon a particular CPU without correctly checking that certain CPU features are actuallypresent. VirtualBox filters what CPU capabilities are presented to the guest operatingsystem. Advanced users can attempt to restrict these virtual CPU capabilities with theVBoxManage --modifyvm --cpuid command; see chapter 8.7.5, Teleporting settings,page 115.
998 VBoxManage8.1 IntroductionAs briefly mentioned in chapter 1.13, Alternative front-ends, page 28, VBoxManage is thecommand-line interface to VirtualBox. With it, you can completely control VirtualBox from thecommand line of your host operating system. VBoxManage supports all the features that thegraphical user interface gives you access to, but it supports a lot more than that. It exposes reallyall the features of the virtualization engine, even those that cannot (yet) be accessed from theGUI. You will need to use the command line if you want to
• use a different user interface than the main GUI (for example, VBoxSDL or the VBoxHead- less server); • control some of the more advanced and experimental configuration settings for a VM.
There are two main things to keep in mind when using VBoxManage: First, VBoxManage mustalways be used with a specific “subcommand”, such as “list” or “createvm” or “startvm”. All thesubcommands that VBoxManage supports are described in detail in chapter 8, VBoxManage, page100. Second, most of these subcommands require that you specify a particular virtual machine afterthe subcommand. There are two ways you can do this:
•"
•settings, including their respective names and UUIDs. Some typical examples of how to control VirtualBox from the command line are listed below:
• 4.0.0 (C) 2005-2010 Oracle Corporation All rights reserved.
100 8 VBoxManage
As can be seen from the above output, a new virtual machine has been created with a new UUID and a new XML settings file.
• To show the configuration of a particular VM, use VBoxManage showvminfo; see chapter 8.4, VBoxManage showvminfo, page 108 for details and an example. • To change settings while a VM is powered off, use VBoxManage modifyvm, e.g. as follows: VBoxManage modifyvm "Windows XP" --memory "512MB"
Usage:
101 8 VBoxManage
102 8 VBoxManage
[--uartmode<1-N> disconnected| server <pipe>| client <pipe>| file <file>| <devicename>] [--guestmemoryballoon <balloonsize in MB>] [--gueststatisticsinterval <seconds>] [--audio none|null|dsound|solaudio|oss|alsa|pulse| oss|pulse|coreaudio] [--audiocontroller ac97|hda|sb16] [--clipboard disabled|hosttoguest|guesttohost| bidirection] [--snapshotfolder default|<path>] [--teleporter on|off] [--teleporterport <port>] [--teleporteraddress <address|empty> [--teleporterpassword <password>]
103 8 VBoxManage
vrdeport <port> | vrdeproperty <name=[value]> | vrdevideo> cpuexecutioncap <1-100>
104 8 VBoxManage
105 8 VBoxManage
copyto|cp <vmname>|<uuid> <source on host> <destination on guest> --username <name> --password <password> [--dryrun] [--follow] [--recursive] [--verbose]
createdir[ectory]|mkdir|md <vmname>|<uuid> <directory to create on guest> --username <name> --password <password> [--parents] [--mode <mode>] [--verbose]
updateadditions <vmname>|<uuid> [--source <guest additions .ISO>] [--verbose]
106 8 VBoxManage
[*|host|<vmname> [<metric_list>]]
Each time VBoxManage is invoked, only one command can be executed. However, a commandmight support several subcommands which then can be invoked in one single call. The followingsections provide detailed reference information on the different commands.
• vms lists all virtual machines currently registered with VirtualBox. By default this displays a compact list with each VM’s name and UUID; if you also specify --long or -l, this will be a detailed list as with the showvminfo command (see below). • runningvms lists all currently running virtual machines by their unique identifiers (UUIDs) in the same format as with vms. • ostypes lists all guest operating systems presently known to VirtualBox, along with the identifiers used to refer to them with the modifyvm command. • hostdvds, hostfloppies, respectively, list DVD, floppy, bridged networking and host-only networking interfaces on the host, along with the name used to access them from within VirtualBox. • bridgedifs, hostonlyifs and dhcpservers, respectively, list bridged network interfaces, host-only network interfaces and DHCP servers currently available on the host. Please see chapter 6, Virtual networking, page 84 for details on these.
• hostinfo displays information about the host system, such as CPUs, memory size and operating system version.
107 8 VBoxManage
• hostcpuids dumps the CPUID parameters for the host CPUs. This can be used for a more fine grained analyis of the host’s virtualization capabilities.
• hddbackends lists all known virtual disk back-ends of VirtualBox. For each such format (such as VDI, VMDK or RAW), this lists the back-end’s capabilities and configuration. • 75. • usbhost. • systemproperties displays some global VirtualBox settings, such as minimum and maxi- mum guest RAM and virtual hard disk size, folder settings and the current authentication library in use.
• extpacks displays all VirtualBox extension packs currently installed; see chapter 1.5, In- stalling VirtualBox and extension packs, page 14 and chapter 8.34, VBoxManage extpack, page 133 for more information.
Name: Windows XPGuest OS: Other/UnknownUUID: 1bf3464d-57c6-4d49-92a9-a5cc3816b7e7Config file: /home/username/.VirtualBox/Machines/Windows XP/Windows XP.xmlMemory size: 512MBVRAM size: 12MBNumber of CPUs: 2Synthetic Cpu: offBoot menu mode: message and menuBoot Device (1): DVDBoot Device (2): HardDiskBoot Device (3): Not AssignedBoot Device (4): Not AssignedACPI: onIOAPIC: onPAE: onTime offset: 0 msHardw. virt.ext: onHardw. virt.ext exclusive: onNested Paging: onVT-x VPID: offState: powered off (since 2009-10-20T14:52:19.000000000)Monitor count: 13D Acceleration: off
108 8 VBoxManage
Shared folders:<none>
Note: When creating a new virtual machine with VBoxManage createvm (see below), you can directly specify the --register option to avoid having to register it separately.
The unregistervm command unregisters a virtual machine. If --delete is also specified, thefollowing;
109 8 VBoxManage
• --name <name>: This changes the VM’s name and possibly renames the internal virtual machine files, as described with VBoxManage createvm above.
• --ostype <ostype>: This specifies what guest operating system is supposed to run in the VM. To learn about the various identifiers that can be used here, use VBoxManage list ostypes.
• --memory <memorysize>: This sets the amount of RAM, in MB, that the virtual machine should allocate for itself from the host. See the remarks in chapter 1.7, Creating your first virtual machine, page 16 for more information. • --vram <vramsize>: This sets the amount of RAM that the virtual graphics card should have. See chapter 3.5, Display settings, page 45 for details. • --acpi on|off; --ioapic on|off: These two determine whether the VM should have ACPI and I/O APIC support, respectively; see chapter 3.4.1, “Motherboard” tab, page 43 for details. • --hardwareuuid <uuid>: The UUID presented to the guest via memory tables (DMI/SMBIOS), hardware and guest properties. By default this is the same as the VM uuid. Useful when cloning a VM. Teleporting takes care of this automatically.
110 8 VBoxManage
• --cpus <cpucount>: This sets the number of virtual CPUs for the virtual machine (see chapter 3.4.2, “Processor” tab, page 44). If CPU hot-plugging is enabled (see below), this then sets the maximum number of virtual CPUs that can be plugged into the virtual ma- chines.• --rtcuseutc on|off: This option lets the real-time clock (RTC) operate in UTC time (see chapter 3.4.1, “Motherboard” tab, page 43).• --cpuhotplug on|off: This enables CPU hot-plugging. When enabled, virtual CPUs can be added to and removed from a virtual machine while it is running. See chapter 9.4, CPU hot-plugging, page 139 for more information.• -.• --cpuexecutioncap <1-100>: This setting controls how much cpu time a virtual CPU can use. A value of 50 implies a single virtual CPU can use up to 50% of a single host CPU.• --synthcpu on|off: This setting determines whether VirtualBox will expose a synthetic CPU to the guest to allow live migration between host systems that differ significantly.• --pae on|off: This enables/disables PAE (see chapter 3.4.2, “Processor” tab, page 44).• --hpet on|off: This enables/disables a High Precision Event Timer (HPET) which can replace the legacy system timers. This is turned off by default. Note that Windows supports a HPET only from Vista onwards.• --hwvirtex on|off: This enables or disables the use of hardware virtualization exten- sions (Intel VT-x or AMD-V) in the processor of your host system; see chapter 10.3, Hard- ware vs. software virtualization, page 155.• --hwvirtexexcl on|off: This specifies whether VirtualBox will make exclusive use of the hardware virtualization extensions (Intel VT-x or AMD-V) in the processor of your host system; see chapter 10.3, Hardware vs. software virtualization, page 155. If you wish to simultaneously share these extensions with other hypervisors, then you must disable this setting. Doing so has negative performance implications.• --nestedpaging on|off: If hardware virtualization is enabled, this additional setting enables or disables the use of the nested paging feature in the processor of your host system; see chapter 10.3, Hardware vs. software virtualization, page 155.• -.• --vtxvpid on|off: If hardware virtualization is enabled, for Intel VT-x only, this addi- tional setting enables or disables the use of the tagged TLB (VPID) feature in the processor of your host system; see chapter 10.3, Hardware vs. software virtualization, page 155.• --accelerate3d on|off: This enables, if the Guest Additions are installed, whether hard- ware 3D acceleration should be available; see chapter 4.4.1, Hardware 3D acceleration (OpenGL and Direct3D 8/9), page 65.•.
111 8 VBoxManage. • --biosbootmenu disabled|menuonly|messageandmenu: This specifies whether the BIOS allows the user to select a temporary boot device. menuonly suppresses the message, but the user can still press F12 to select a temporary boot device. • -.
• --snapshotfolder default|<path>: This allows you to specify the folder in which snap- shots will be kept for a virtual machine. • --firmware efi|bios: Specifies which firmware is used to boot particular virtual ma- chine: EFI or BIOS. Use EFI only if your fully understand what you’re doing. • -.8.1, Memory ballooning, page 70.
112 8 VBoxManage
• --macaddress<1-N> auto|<mac>: With this option you can set the MAC address of the virtual network card. Normally, each virtual network card is assigned a random address by VirtualBox at VM creation. • - 85 and the VDE documentation).
• --natpf<1-N> delete <name>: This option deletes a NAT port-forwarding rule (please see chapter 6.3.1, Configuring port forwarding with NAT, page 86 for details). • --nattftpprefix<1-N> <prefix>: This option defines a prefix for the built-in TFTP server, i.e. where the boot file is located (please see chapter 6.3.2, PXE booting with NAT, page 87 and chapter 9.9.2, Configuring the boot server (next server) of a NAT network inter- face, page 145 for details). • --nattftpfile<1-N> <bootfile>: This option defines the TFT boot file (please see chap- ter 9.9.2, Configuring the boot server (next server) of a NAT network interface, page 145 for details). • --nattftpserver<1-N> <tftpserver>: This option defines the TFTP server address to boot from (please see chapter 9.9.2, Configuring the boot server (next server) of a NAT network interface, page 145 for details). • --natdnspassdomain<1-N> on|off: This option specifies whether the built-in DHCP server passes the domain name for network name resolution.
• --natdnsproxy<1-N> on|off: This option makes the NAT engine proxy all guest DNS requests to the host’s DNS servers (please see chapter 9.9.5, Enabling DNS proxy in NAT mode, page 145 for details).
113 8 VBoxManage
• --natdnshostresolver<1-N> on|off: This option makes the NAT engine use the host’s resolver mechanisms to handle DNS requests (please see chapter 9.9.5, Enabling DNS proxy in NAT mode, page 145 for details). • --natnatsettings<1-N> [<mtu>],[<socksnd>],[<sockrcv>],[<tcpsnd>], [<tcprcv>]: This option controls several NAT settings (please see chapter 9.9.3, Tuning TCP/IP buffers for NAT, page 145 for details). • --nataliasmode<1-N> default|[log],[proxyonly],[sameports]: This option de- fines behaviour of NAT engine core: log - enables logging, proxyonly - switches of aliasing mode makes NAT transparent, sameports enforces NAT engine to send packets via the same port as they originated on, default - disable all mentioned modes above . (please see chap- ter 9.9.7, Configuring aliasing of the NAT engine, page 146 for details).
8.7.3 Serial port, audio, clipboard, remote desktop and USB settingsThe following other hardware settings are available through VBoxManage modifyvm:
• --uart<1-N> off|<I/O base> <IRQ>: With this option you can configure virtual serial ports for the VM; see chapter 3.9, Serial ports, page 48 for an introduction.
• --uartmode<1-N> <arg>: This setting controls how VirtualBox connects a given virtual serial port (previously configured with the --uartX setting, see above) to the host on which the virtual machine is running. As described in detail in chapter 3.9, Serial ports, page 48,. • --audio none|null|oss: With this option, you can set whether the VM should have audio support. • --clipboard disabled|hosttoguest|guesttohost|bidirectional: With this set- ting, you can select whether the guest operating system’s clipboard should be shared with the host; see chapter 3.3, General settings, page 42. This requires that the Guest Additions be installed in the virtual machine.
• --monitorcount <count>: This enables multi-monitor support; see chapter 3.5, Display settings, page 45. • --usb on|off: This option enables or disables the VM’s virtual USB controller; see chapter 3.10.1, USB settings, page 49 for details.
• --usbehci on|off: This option enables or disables the VM’s virtual USB 2.0 controller; see chapter 3.10.1, USB settings, page 49 for details.
114 8 VBoxManage
• --vrde on|off: With the VirtualBox graphical user interface, this enables or disables the VirtualBox remote desktop extension (VRDE) server. Note that if you are using VBoxHeadless (see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 92), VRDE is enabled by default. • --vrdeport default|<ports>: A port or a range of ports the VRDE server can bind to; “default” or “0” means port 3389, the standard port for RDP. You can specify a comma- separated list of ports or ranges of ports. Use a dash between two port numbers to spec- ify a range. The VRDE server will bind to one of available ports from the specified list. Only one machine can use a given port at a time. For example, the option --vrdeport 5000,5010-5012 will tell the server to bind to one of following ports: 5000, 5010, 5011 or 5012.
• --vrdeaddress <IP address>: The IP address of the host network interface the VRDE server will bind to. If specified, the server will accept connections only on the specified host network interface. • --vrdeauthtype null|external|guest: This allows you to choose whether and how authorization will be performed; see chapter 7.1.5, RDP authentication, page 95 for details.
• --vrdemulticon on|off: This enables multiple connections to the same VRDE server, if the server supports this feature; see chapter 7.1.7, Multiple connections to the VRDP server, page 96. • --vrdereusecon on|off: This specifies the VRDE server behavior when multiple con- nections are disabled. When this option is enabled, the server will allow a new client to connect and will drop the existing connection. When this option is disabled (this is the de- fault setting), a new connection will not be accepted if there is already a client connected to the server. • --vrdevideochannel on|off: This enables video redirection, if it is supported by the VRDE server; see chapter 7.1.9, VRDP video redirection, page 97.
• -. • - “0.0.0.0”, which means any address.
115 8 VBoxManage
Note: Currently, the password is stored without encryption (i.e. in clear text) in the XML machine configuration file.
• --cpuid <leaf> <eax> <ebx> <ecx> <edx>: Advanced users can use this command be- fore hard- ware dependent; please refer to the AMD or Intel processor manuals.
116 8 VBoxManage
As you can see, the individual configuration items are numbered, and depending on their typesupport different command-line options. The import subcommand can be directed to ignoremany such items with a --vsys X --unit Y --ignore option, where X is the number of thevirtual system (zero unless there are several virtual system descriptions in the appliance) and Ythe beconnected to, with the default coming from the OVF file. You can combine several items for the same virtual system behind the same --vsys option. Forexample, to import a machine as described in the OVF, but without the sound card and withoutthe USB controller, and with the disk image connected to the IDE controller instead of the SCSIcontroller, use this:VBoxManage import WindowsXp.ovf --vsys 0 --unit 5 --ignore --unit 6 --ignore --unit 11 --controller 10
Note: This is provided for backwards compatibility only. We recommend to start virtual machines directly by running the respective front-end, as you might otherwise miss im- portant error and state information that VirtualBox may display on the console. This is especially important for front-ends other than VirtualBox, our graphical user in- terface, because those cannot display error messages in a popup window. See chapter 7.1.2, VBoxHeadless, the remote desktop server, page 92 for more information.
The optional --type specifier determines whether the machine will be started in a window(GUI mode, which is the default) or whether the output should go through VBoxHeadless, withVRDE enabled or not; see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 92 formore information. The list of types is subject to change, and it’s not guaranteed that all types areaccepted by any product variant. The following values are allowed:
117 8 VBoxManage
118 8 VBoxManage
•. • vrde on|off lets you enable or disable the VRDE server, if it is installed. • vrdeport default|<ports> changes the port or a range of ports that the VRDE server can bind to; “default” or “0” means port 3389, the standard port for RDP. For details, see the description for the --vrdeport option in chapter 8.7.3, Serial port, audio, clipboard, remote desktop and USB settings, page 114. • setvideomodehint requests that the guest system change to a particular video mode. This requires that the Guest Additions be installed, and will not work for all guest systems.
• The setcredentials operation is used for remote logons in Windows guests. For details, please refer to chapter 9.2, Automated guest logons, page 136. •.8.1, Memory ballooning, page 70. • The cpuexecutioncap <1-100>: This operation controls how much cpu time a virtual CPU can use. A value of 50 implies a single virtual CPU can use up to 50% of a single host CPU.
119 8 VBoxManage
The delete operation deletes a snapshot (specified by name or by UUID). This can take awhile to finish since the differencing images associated with the snapshot might need to bemerged with their child differencing images. The restore operation will restore the given snapshot (specified by name or by UUID) byresetting the virtual machine’s settings and current state to that of the snapshot. The previouscurrent state of the machine will be lost. After this, the given snapshot becomes the new “current”snapshot so that subsequent snapshots are inserted under the snapshot from which was restored. The restorecurrent operation is a shortcut to restore the current snapshot (i.e. the snapshotfrom which the current state is derived). This subcommand is equivalent to using the “restore”subcommand with the name or UUID of the current snapshot, except that it avoids the extra stepof determining that name or UUID. With the edit operation, you can change the name or description of an existing snapshot. With the showvminfo operation, you can view the virtual machine settings that were storedwith an existing snapshot.
A number of parameters are commonly required; the ones at the end of the list are requiredonly for iSCSI targets (see below). The common parameters are:.
120 8 VBoxManage
storagectl Name of the storage controller. Mandatory. The list of the storage controllers cur- rently attached to a VM can be obtained with VBoxManage showvminfo; see chapter 8.4, VBoxManage showvminfo, page 108.port The number of the storage controller’s port which is to be modified. Mandatory.device The number of the port’s device which is to be modified. Mandatory.: • “none”: Any existing device should be removed from the given slot. • “emptydrive”: For a virtual DVD or floppy drive only, this makes the device slot be- haves like a removeable drive into which no media has been inserted. • If a UUID is specified, it must be the UUID of a storage medium that is already known to VirtualBox (e.g. because it has been attached to another virtual machine). See chapter 8.3, VBoxManage list, page 107 for how to list known media. This medium is then attached to the given device slot. • If a filename is specified, it must be the full path of an existing disk image (ISO, RAW, VDI, VMDK or other), which is then attached to the given device slot. • “host:<drive>“: For a virtual DVD or floppy drive only, this connects the given device slot to the specified DVD or floppy drive on the host computer. •  77 for details.
comment Any description that you want to have stored with this medium (optional; for exam- ple, for an iSCSI target, “Big storage server downstairs”). This is purely descriptive and not needed for the medium to function correctly.passthrough For a virtual DVD drive only, you can enable DVD writing support (currently ex- perimental; see chapter 5.9, CD/DVD support, page 82).bandwidthgroup Sets the bandwidth group to use for the given device; see chapter 5.8, Limiting bandwidth for disk images, page 81 82 for details.
When “iscsi” is used with the --medium parameter for iSCSI support – see chapter 5.10, iSCSIservers, page 83 –, additional parameters must or can be used:
target Target name string. This is determined by the iSCSI target and used to identify the storage resource; required.
121 8 VBoxMan con- figuration which is described in chapter 9.6.3, Access iSCSI targets via Internal Networking, page 143. 72, by default, this is the case for SATA ports 1-4; with this command, you can map four IDE channels to any of the 30 supported SATA ports. 81.remove Removes the storage controller from the VM config.
122 8 VBoxManage
See chapter 5.8, Limiting bandwidth for disk images, page 81 for an introduction to bandwidthlimits..
Note: For compatibility with earlier versions of VirtualBox, the “showvdiinfo” com- mand is also supported and mapped internally to the “showhdinfo” command.
Note: For compatibility with earlier versions of VirtualBox, the “createvdi” command is also supported and mapped internally to the “createhd” command.
123 8 VBoxManage
Note: Despite the “hd” in the subcommand name, the command works with all disk images, not only hard disks. For compatibility with earlier versions of VirtualBox, the “modifyvdi” command is also supported and mapped internally to the “modifyhd” com- mand.
• With the --type argument, you can change the type of an existing image between the normal, immutable, write-through and other modes; see chapter 5.4, Special image write modes, page 77 for details. • For immutable (differencing) hard disks only, the --autoreset on|off option determines whether the disk is automatically reset on every VM startup (again, see chapter 5.4, Special image write modes, page 77). The default is “on”. • With the --compact option, can be used to compact disk images, i.e. remove blocks that only contains zeroes. This will shrink a dynamically expanding image again; it will re- duce -c in the guest to zero the free disk space before compressing the virtual disk image. Please note that compacting is currently only available for VDI images. A similar effect can be achieved by zeroing out free blocks and then cloning the disk to any other dynamically expanding format. You can use this workaround until compacting is also supported for disk formats other than VDI. • The –resize option allows you to expand the capacity of an existing image; this increases the logical size of a virtual disk without affecting the physical size much.3 This currently works only for the VDI and VHD formats, and only for the dynamically expanding variants. For example, if you originally created a 10G disk which is now full, you can use the –resize command to add more space to the virtual disk without having to create a new image and copy all data from within a virtual machine.
124 8 VBoxManage por- tion.
125 8 VBoxManage
would associate the string “2006.01.01” with the key installdate for the virtual machine Fe-dora5, and “2006.02.02” on the machine SUSE10. You could retrieve the information as follows:VBoxManage getextradata Fedora5 installdate
Value: 2006.01.01
machinefolder This specifies the default folder in which virtual machine definitions are kept; see chapter 10.1, Where VirtualBox stores its files, page 151 for details.vrdeauthlibrary This specifies which library to use when “external” authentication has been selected for a particular virtual machine; see chapter 7.1.5, RDP authentication, page 95 for details.
websrvauthlibrary This specifies which library the web service uses to authenticate users. For details about the VirtualBox web service, please refer to the separate VirtualBox SDK refer- ence (see chapter 11, VirtualBox programming interfaces, page 161).vrdelibrary This specifies which library implements the VirtualBox Remote Desktop Extension.
126 8 VBoxManage
place. Otherwise the new filter will be added onto the end of the list. The target parameterselects the virtual machine that the filter should be attached to or use “global” to apply it to allvirtual machines. name is a name for the new filter and for global filters, action says whether toallow machines access to devices that fit the filter description (“hold”) or not to give them access(“ignore”). In addition, you should specify parameters to filter by. You can find the parametersfor devices attached to your system using VBoxManage list usbhost. Finally, you can specifywhether the filter should be active, and for local filters, whether they are for local devices, remote(over an RDP connection) or either. When you modify a USB filter using usbfilter modify, you must specify the filter by in-dex (see the output of VBoxManage list usbfilters to find global filter indexes and that ofVBoxManage showvminfo to find indexes for individual machines) and by target, which is ei-ther a virtual machine or “global”. The properties which can be changed are the same as forusbfilter add. To remove a filter, use usbfilter remove and specify the index and the tar-get.
•”. • get <vm>: This retrieves the value of a single property only. If the property cannot be found (e.g. because the guest is not running), this will print “No value set¡‘. • set <vm> <property> [<value> [--flags <flags>]]: This allows you to set a guest property by specifying the key and value. If <value> is omitted, the property is deleted.
127 8 VBoxManage
With --flags you can optionally specify additional behavior (you can combine several by separating them with commas): – TRANSIENT: the value will not be stored with the VM data when the VM. • wait <vm> <pattern> --timeout <timeout>: This waits for a particular value de- scribed by “pattern” to change or to be deleted or created. The pattern rules are the same as for the “enumerate” subcommand above.
The following subcommands are available (where <vm>, in each case, can either be a VM nameor a VM UUID, as with the other VBoxManage commands):
• execute, which allows for executing a program/script (process) which is already installed and runnable on the guest. This command only works while a VM is up and running and has the following syntax: VBoxManage guestcontrol exec[ute] <vmname>|<uuid> <path to program> --username <name> --password <password> [--arguments "<arguments>"] [--environment "<NAME>=<VALUE> [<NAME>=<VALUE>]"] [--flags <flags>] [--timeout <msec>] [--verbose] [--wait-for exit,stdout,stderr||]
128 8 VBoxManage
. –username <name> Name of the user the process should run under. This user must exist on the guest OS. –password <password> Password of the user account specified with --username. If not given, an empty password is assumed. –verbose Tells VBoxManage to be more verbose. –wait-for <action> Tells VBoxManage to wait for a certain action to happen and react to it. The following actions are available: exit Waits until the process ends and outputs its exit code along with the exit rea- son 14, Known limitations, page 178 for more information.
Examples: VBoxManage --nologo guestcontrol execute "My VM" "/bin/ls" --arguments "-l /usr" --username foo --password bar --wait-for stdout
Note that the double backslashes in the second example are only required on Unix hosts.• copyto, which allows copying files from the host to the guest (only with installed Guest Additions 4.0 and later). VBoxManage copyto|cp <vmname>|<uuid> <source on host> <destination on guest> --username <name> --password <password> [--dryrun] [--follow] [--recursive] [--verbose]
129 8 VBoxManage
• createdirectory, which allows copying files from the host to the guest (only with in- stalled Guest Additions 4.0 and later). VBoxManage createdir[ectory]|mkdir|md <vmname>|<uuid> <directory to create on guest> [--username "<name>"] [--password "<password>"] [--parents] [--mode <mode>] [--verbose]
• With dumpguestcore --filename <name>, you can create a system dump of the running VM, which will be written into the given file. This file will have the standard ELF core format (with custom sections); see chapter 12.1.4, VM core format, page 165. •.
130 8 VBoxManage
• The statistics command can be used to display VMM statistics on the command line. The --reset option will reset statistics. The affected statistics can be filtered with the --pattern option, which accepts DOS/NT-style wildcards (? and *).
Metric collection can only be enabled for started VMs. Collected data and collection settingsfor a particular VM will disappear as soon as it shuts down. Use VBoxManage metrics listsubcommand to see which metrics are currently available. You can also use --list option withany subcommand that modifies metric settings to find out which metrics were affected. Note that the VBoxManage metrics setup subcommand discards all samples that may havebeen previously collected for the specified set of objects and metrics. To enable or disable metrics collection without discarding the data VBoxManage metricsenable and VBoxManage metrics disable subcommands can be used. Note that these sub-commands expect metrics, not submetrics, like CPU/Load or RAM/Usage as parameters. In otherwords enabling CPU/Load/User while disabling CPU/Load/Kernel is not supported. The host and VMs have different sets of associated metrics. Available metrics can be listedwith VBoxManage metrics list subcommand. A complete metric name may include an aggregate function. The name has the following form:Category/Metric[/SubMetric][:aggregate]. For example, RAM/Usage/Free:min stands forthe minimum amount of available memory over all retained data if applied to the host object. Subcommands may apply to all objects and metrics or can be limited to one object or/and alist of metrics. If no objects or metrics are given in the parameters, the subcommands will applyto all available metrics of all objects. You may use an asterisk (“*“) to explicitly specify that thecommand should be applied to all objects or metrics. Use “host” as the object name to limit thescope of the command to host-related metrics. To limit the scope to a subset of metrics, use ametric list with names separated by commas. For example, to query metric data on the CPU time spent in user and kernel modes by thevirtual machine named “test”, you can use the following command:VBoxManage metrics query test CPU/Load/User,CPU/Load/Kernel
131 8 VBoxMan.
•>.
•.3, VBoxManage list, page 107 above).
The following additional parameters are required when first adding a DHCP server:
132 8 VBoxManage
Finally, you must specify --enable or the DHCP server will be created in the disabled state,doing nothing. After this, VirtualBox will automatically start the DHCP server for given internal or host-onlynetworkhost-only network. To modify the settings of a DHCP server created earlier with VBoxManage dhcpserver add,you can use VBoxManage dhcpserver modify for a given network or host-only interface name.
1339 Advanced topics9.1 VBoxSDL, the simplified VM displayer9.1.1 IntroductionVBoxSDL is a simple graphical user interface (GUI) that lacks the nice point-and-click supportwhich VirtualBox, our main GUI, provides. VBoxSDL is currently primarily used internally fordebugging VirtualBox and therefore not officially supported. Still, you may find it useful forenvironments where the virtual machines are not necessarily controlled by the same person thatuses the virtual machine.
As you can see in the following screenshot, VBoxSDL does indeed only provide a simple win-dow that contains only the “pure” virtual machine, without menus or other controls to click uponand no additional indicators of virtual machine activity:
To start a virtual machine with VBoxSDL instead of the VirtualBox GUI, enter the following ona command line:VBoxSDL --startvm <vm>
where <vm> is, as usual with VirtualBox command line parameters, the name or UUID of anexisting virtual machine.
134 9 Advanced topics
system might fool the user into thinking that it is either a different system (which might have ahigher security level) or it might present messages on the screen that appear to stem from thehost operating system. In order to protect the user against the above mentioned security risks, the secure labelingfeature has been developed. Secure labeling is currently available only for VBoxSDL. Whenenabled, a portion of the display area is reserved for a label in which a user defined message isdisplayed. The label height in set to 20 pixels in VBoxSDL. The label font color and backgroundcolor can be optionally set as hexadecimal RGB color values. The following syntax is used toenablefont size than 12 point use the parameter --seclabelsiz. The label text can be set withVBoxManage setextradata "VM name" "VBoxSDL/SecureLabel" "The Label"
For example, in order to start Linux with 1024 x 748 x 16, the standard mode 0x117 (1024x 768 x 16) is used as a base. The Linux video mode kernel parameter can then be calculatedusing:vga = 0x200 | 0x117 + 0x30vga = 839
The reason for duplicating the standard modes instead of only supplying the adjusted modesis that most guest operating systems require the standard VESA modes to be fixed and refuse tostart with different modes. When using the X.org VESA driver, custom modelines have to be calculated and added to theconfiguration (usually in /etc/X11/xorg.conf. A handy tool to determine modeline entries canbe found at.)
135 9 Advanced topics
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDLL
Note: The VirtualBox GINA module is implemented as a wrapper around the standard Windows GINA module (MSGINA.DLL). As a result, it will most likely not work correctly with 3rd party GINA modules.
To manually install the VirtualBox credential module, extract the Guest Additions (see chapter4.2.1.4, Manual file extraction, page 56) and copy the file VBoxCredProv.dll to the WindowsSYSTEM32 directory. Then,
with all default values (the key named (Default) in each key) set to VBoxCredProv. Afterthat a new string namedHKEY_CLASSES_ROOT\CLSID\{275D3BCC-22BB-4948-A7F6-3A3054EBA92B}\InprocServer32\ThreadingModel
While the VM is running, the credentials can be queried by the VirtualBox logon modules(GINA or credential provider) using the VirtualBox Guest Additions device driver. When Win-dows is in “logged out” mode, the logon modules will constantly poll for credentials and if they
136 9 Advanced topics
are present, a logon will be attempted. After retrieving the credentials, the logon modules willerase them so that the above command will have to be repeated for subsequent logons. For security reasons, credentials are not stored in any persistent manner and will be lost whenthe VM is reset. Also, the credentials are “write-only”, i.e. there is no way to retrieve thecredentials from the host side. Credentials can be reset from the host side by setting emptyvalues. Depending on the particular variant of the Windows guest, the following restrictions apply:
1. For Windows XP guests, the logon subsystem needs to be configured to use the classic logon dialog as the VirtualBox GINA module does not support the XP-style welcome dialog. 2. For Windows Vista and Windows 7 guests, the logon (internally, Windows never renames user accounts).
The following command forces VirtualBox to keep the credentials after they were read by theguest and on VM reset:VBoxManage setextradata "Windows XP" VBoxInternal/Devices/VMMDev/0/Config/KeepCredentials 1
Note that this is a potential security risk as a malicious application running on the guest couldrequest this information using the proper interface.
Note: The pam_vbox.so only supports the auth primitive. Other primitives such as account, session or password are not supported.
The pam_vbox.so module is shipped as part of the Guest Additions but it is not installedand/or activated on the guest OS by default. In order to install it, it has to be copied from/opt/VBoxGuestAdditions-<version>/lib/VBoxGuestAdditions/ to the security modulesdirectory, usually /lib/security/. Please refer to your guest OS documentation for the correctPAM module directory. For example, to use pam_vbox.so with a Ubuntu Linux guest OS and GDM (the GNOMEDesktop Manager) to logon users automatically with the credentials passed by the host, theguest OS has to be configured like the following:
1. The pam_vbox.so module has to be copied to the security modules directory, in this case it is /lib/security. 2. Edit the PAM configuration file for GDM found at /etc/pam.d/gdm, adding the line auth requisite pam_vbox.so at the top. Additionaly, in most Linux distributions there is a file called /etc/pam.d/common-auth. This file is included in many other services (like the GDM file mentioned above). There you also have to add add the line auth requisite pam_vbox.so.
137 9 Advanced topics
Warning: An incorrectly configured PAM stack can effectively prevent you from logging into your guest system!
To make deployment easier, you can pass the argument debug right after the pam_vbox.sostatement. Debug log output will then be recorded using syslog.
Warning: At present, the GDM display manager only retrieves credentials at startup so unless the credentials have been supplied to the guest before GDM starts, automatic logon will not work. This limitation needs to be addressed by the GDM developers or another display manager must be used.
Note: Specifying the location of “sysprep.exe” is not possible – instead the following paths are used (based on the operating system):
The Guest Additions will automatically use the appropriate path to execute the system preparation tool.
138 9 Advanced topics
After that, the –cpus option specifies the maximum number of CPUs that the virtual machinecan have:VBoxManage modifyvm "VM name" - name" --plugcpu 3VBoxManage modifyvm "VM name" --unplugcpu 3
See chapter 8.7, VBoxManage modifyvm, page 110 and chapter 8.11, VBoxManage controlvm,page 118 for details. With Linux guests, the following applies: To prevent ejection while the CPU is still used it hasto be ejected from within the guest before. The Linux Guest Additions contain a service whichreceives hot-remove events and ejects the CPU. Also, after a CPU is added to the VM it is notautomatically used by Linux. The Linux Guest Additions service will take care of that if installed.If not a CPU can be started with the following command:echo 1 > /sys/devices/system/cpu/cpu<id>/online
139 9 Advanced topics
The VESA mode IDs for custom video modes start at 0x160. In order to use the above definedcustom video mode, the following command line has be supplied to Linux:vga = 0x200 | 0x160vga = 864
For guest operating systems with VirtualBox Guest Additions, a custom video mode can be setusing the video mode hint feature.
restores the default settings. Note that these settings apply globally to all guest systems, notjust to a single machine..
140 9 Advanced topics
Raw hard disk access – both for entire disks and individual partitions – is implemented as partof the VMDK image format support. As a result, you will need to create a special VMDK imagefile which defines where the data will be stored. After creating such a special VMDK image, youcan use it like a regular virtual disk image. For example, you can use the Virtual Media Manager(chapter 5.3, The Virtual Media Manager, page 75) or VBoxManage to assign the image to a virtualmachine.
This creates the image /path/to/file.vmdk (must be absolute), and all data will be read andwritten from /dev/sda. On a Windows host, instead of the above device specification, use e.g. \\.\PhysicalDrive0.On a Mac OS X host, instead of the above device specification use e.g. /dev/disk1. Note thaton OS X you can only get access to an entire disk if no volume is mounted from it. Creating the image requires read/write access for the given device. Read/write access is alsolater needed when using the image from a virtual machine. Just like with regular disk images, this does not automatically register the newly created image e.g.VBoxManage storageattach WindowsXP --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium /path/to/file.vmdk
When this is done the selected virtual machine will boot from the specified physical disk.
As you can see, the command is identical to the one for “full hard disk” access, except for theadditional -partitions parameter. This example would create the image /path/to/file.vmdk(which, again, must be absolute), and partitions 1 and 5 of /dev/sda would be made accessibleto the guest.
141 9 Advanced topics
VirtualBox uses the same partition numbering as your Linux host. As a result, the numbersgiven in the above example would refer to the first primary partition and the first logical drive inthe extended partition, respectively. On a Windows host, instead of the above device specification, use e.g. \\.\PhysicalDrive0.On a Mac OS X host, instead of the above device specification use e.g. /dev/disk1. Note thaton OS X you can only use partitions which are not mounted (eject the respective volume first).Partition numbers are the same on Linux, Windows and Mac OS X hosts. The numbers for the list of partitions can be taken from the output ofVBoxManage internalcommands listpartitions -rawdisk /dev/sda
The output lists the partition types and sizes to give the user enough information to identify thepartitions alsolater needed when using the image from a virtual machine. If this is not feasible, there is a specialvariant for raw partition access (currently only available on Linux hosts) that avoids having togive the current user access to the entire disk. To set only to theindividual partitions (in the example /dev/sda1 and /dev/sda5). As a consequence, read/writeaccess is only required for the affected partitions, not for the entire disk. During creation how-ever, read-only access to the entire disk is required to obtain the partitioning information. In some configurations it may be necessary to change the MBR code of the created image, e.g.to replace the Linux boot loader that is used on the host by another boot loader. This allows e.g.the guest to boot directly to Windows, while the host boots Linux from the “same” disk. For thispurpose the -mbr parameter is provided. It specifies a file name from which to take the MBRcode. The partition table is not modified at all, so a MBR file from a system with totally differentpartitioning can be used. use inVirtualBox by adding -register to the respective command line. The image will then immedi-ately image issuccessfully created.
142 9 Advanced topics
The serial number is a 20 byte alphanumeric string, the firmware revision an 8 byte alphanu-meric string and the model number a 40 byte alphanumeric string. Instead of “Port0” (referringto the first port), specify the desired SATA hard disk port. Additional three parameters are needed for CD/DVD drives to report the vendor product data:VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIVendorId" "vendor"VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIProductId" "product"VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIRevision" "revision"
The vendor id is an 8 byte alphanumeric string, the product id an 16 byte alphanumeric stringand the revision a 4 byte alphanumeric string. Instead of “Port0” (referring to the first port),specify the desired SATA hard disk port.
Finally the iSCSI disk must be attached with the --intnet option to tell the iSCSI initiator touse internal networking:VBoxManage storageattach ... --medium iscsi --server 10.0.9.30 --target iqn.2008-12.com.sun:sampletarget --intnet
Compared to a “regular” iSCSI setup, IP address of the target must be specified as a numericIP address, as there is no DNS resolver for internal networking. The virtual machine with the iSCSI target should be started before the VM using it is poweredon. If a virtual machine using an iSCSI disk is started without having the iSCSI target poweredup, it can take up to 200 seconds to detect this situation. The VM will fail to power up.
143 9 Advanced topics
In order to run more VMs, you will need to bump the semaphore ID limit of the VBoxSVCprocess. Execute as root the prctl command as shown below. The process ID of VBoxSVC canbe obtained using the ps list command.prctl -r -n project.max-sem-ids -v 2048 <pid-of-VBoxSVC>
Note: For backwards compatibility, the old setextradata statements, whose descrip- tion is retained below from the old version of the manual, take precedence over the new way of configuring serial ports. As a result, if configuring serial ports the new way doesn’t work, make sure the VM in question does not have old configuration data such as below still active.
The old sequence of configuring a serial port used the following 6 commands:VBoxManage setextradata "VM name" "VBoxInternal/Devices/serial/0/Config/IRQ" 4VBoxManage setextradata "VM name" "VBoxInternal/Devices/serial/0/Config/IOBase" 0x3f8VBoxManage setextradata "VM name" "VBoxInternal/Devices/serial/0/LUN#0/Driver" CharVBoxManage setextradata "VM name" "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Driver" NamedPipeVBoxManage setextradata "VM name" "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Config/Location" "\\.\pipe\vboxCOM1"VBoxManage setextradata "VM name" "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Config/IsServer" 1
This sets up a serial port in the guest with the default settings for COM1 (IRQ 4, I/O address0x3f8) and the Location setting assumes that this configuration is used on a Windows host,because the Windows named pipe syntax is used. Keep in mind that on Windows hosts a namedpipe must always start with \\.\pipe\. On Linux the same config settings apply, except thatthe path name for the Location can be chosen more freely. Local domain sockets can be placedanywhere, provided the user running VirtualBox has the permission to create a new file in thedirectory. The final command above defines that VirtualBox acts as a server, i.e. it creates thenamed pipe itself instead of connecting to an already existing one.
144 9 Advanced topics
This command would reserve the network addresses from 192.168.0.0 to 192.168.254.254for the first NAT network instance of “VM name”. The guest IP would be assigned to192.168.0.15 and the default gateway could be found at 192.168.0.2.
9.9.2 Configuring the boot server (next server) of a NAT network interfaceFor network booting in NAT mode, by default VirtualBox uses a built-in TFTP server at the IPaddress 10.0.2.3. This default behavior should work fine for typical remote-booting scenarios.However, it is possible to change the boot server IP and the location of the boot image with thefollowing commands:VBoxManage modifyvm "VM name" --nattftpserver1 10.0.2.2VBoxManage modifyvm "VM name" --nattftpfile1 /srv/tftp/boot/MyPXEBoot.pxe
This example illustrates tuning the NAT settings. The first parameter is the MTU, then the sizeof the socket’s send buffer and the size of the socket’s receive buffer, the initial size of the TCPsend window, and lastly the initial size of the TCP receive window. Note that specifying zeromeans fallback to the default value. Each of these buffers has a default size of 64KB and default MTU is 1500.
After this, all outgoing traffic will be sent through the interface with the IP address 10.45.0.2.Please make sure that this interface is up and running prior to this assignment.
145 9 Advanced topics
Note that this setting is similar to the DNS proxy mode, however whereas the proxy modejust forwards DNS requests to the appropriate servers, the resolver mode will interpret the DNSrequests and use the host’s DNS API to query the information and return it to the guest.
andVBoxManage modifyvm "Linux Guest" --nataliasmode sameports
The first example disables aliasing and switches NAT into transparent mode, the second exam-ple enforces preserving of port values. These modes can be combined if necessary.
If a DMI string is not set, the default value of VirtualBox is used. To set an empty string use"<EMPTY>".
146 9 Advanced topics
Note that in the above list, all quoted parameters (DmiBIOSVendor, DmiBIOSVersion butnot DmiBIOSReleaseMajor) are expected to be strings. If such a string is a valid number,the parameter is treated as number and the VM will most probably refuse to start with anVERR_CFGM_NOT_STRING error. In that case, use "string:<value>", for instance
Changing this information can be necessary to provide the DMI information of the host to theguest to prevent Windows from asking for a new product key. On Linux hosts the DMI BIOSinformation can be obtained withdmidecode -t0
Note that if you use the special TSC handling mode with a guest operating system which is verystrict about the consistency of time sources you may get a warning or error message about thetiming inconsistency. It may also cause clocks to become unreliable with some guest operatingsystems depending on they use the TSC.
The above example will double the speed of the guest clock whileVBoxManage setextradata "VM name" "VBoxInternal/TM/WarpDrivePercentage" 50
147 9 Advanced topics
will halve the speed of the guest clock. Note that changing the rate of the virtual clock canconfuse the guest and can even lead to abnormal guest behavior. For instance, a higher clockrate means shorter timeouts for virtual devices with the result that a slightly increased responsetime of a virtual device due to an increased host load can cause guest failures. Note furtherthat any time synchronization mechanism will frequently try to resynchronize the guest clockwith the reference clock (which is the host clock if the VirtualBox Guest Additions are active).Therefore any time synchronization should be disabled if the rate of the guest clock is changed asdescribed above (see chapter 9.11.3, Tuning the Guest Additions time synchronization parameters,page 148).
--timesync-interval Specifies the interval at which to synchronize the time with the host. The default is 10000 ms (10 seconds).--timesync-min-adjust The minimum absolute drift value measured in milliseconds to make adjustments for. The default is 1000 ms on OS/2 and 100 ms elsewhere.--timesync-latency-factor The factor to multiply the time query latency with to calculate the dynamic minimum adjust time. The default is 8 times, that means in detail: Measure the time it takes to determine the host time (the guest has to contact the VM host service which may take some time), multiply this value by 8 and do an adjustment only if the time difference between host and guest is bigger than this value. Don’t do any time adjustment otherwise.--timesync-max-latency The max host timer query latency to accept. The default is 250 ms.
--timesync-set-on-restore 0|1 Set the time after the VM was restored from a saved state when passing 1 as parameter (default). Disable by passing 0. In the latter case, the time will be adjusted smoothly which can take a long time.
All these parameters can be specified as command line parameters to VBoxService as well.
148 9 Advanced topics
Once you make sure all vboxnet interfaces are unplumbed, remove the driver using:rem_drv vboxnet
then edit the file /platform/i86pc/kernel/drv/vboxnet.conf and add a line for the newinterfaces:name="vboxnet" parent="pseudo" instance=1;name="vboxnet" parent="pseudo" instance=2;
Add as many of these lines as required and make sure “instance” number is uniquely incre-mented. Next reload the vboxnet driver using:add_drv vboxnet
Now plumb all the interfaces using ifconfig vboxnetX plumb (where X can be 0, 1 or 2 in thiscase) and once plumbed you can then configure the interface like any other network interface. To make your newly added interfaces’ settings persistent across reboots you will need to editthe files /etc/netmasks, and if you are using NWAM /etc/nwam/llp and add the appropriateentries to set the netmask and static IP for each of those interfaces. The VirtualBox installer onlyupdates these configuration files for the one “vboxnet0” interface it creates by default.
You can specify which directory to use for core dumps with this command:VBoxManage setextradata "VM name" VBoxInternal2/CoreDumpDir <path-to-directory>
Make sure the directory you specify is on a volume with sufficient free space and that theVirtualBox process has sufficient permissions to write files to this directory. If you skip thiscommand and don’t specify any core dump directory, the current directory of the VirtualBox exe-cutable will be used (which would most likely fail when writing cores as they are protected withroot permissions). It is recommended you explicity set a core dump directory. You must specify when the VirtualBox CoreDumper should be triggered. This is done using thefollowing commands:VBoxManage setextradata "VM name" VBoxInternal2/CoreDumpReplaceSystemDump 1VBoxManage setextradata "VM name" VBoxInternal2/CoreDumpLive 1
At least one of the above two commands will have to be provided if you have enabled theVirtualBox CoreDumper. Setting CoreDumpReplaceSystemDump sets up the VM to override the host’s core dumpingmechanism and in the event of any crash only the VirtualBox CoreDumper would produce thecore file. Setting CoreDumpLive sets up the VM to produce cores whenever the VM receives a SIGUSR2signal. After producing the core file, the VM will not be terminated and will continue to run. Youcan then take cores of the VM process using:kill -s SIGUSR2 <VM-process-id>
Core files produced by the VirtualBox CoreDumper are of the form core.vb.<ProcessName>.<ProcessID>,e.g.core.vb.VBoxHeadless.11321.
149 9 Advanced topics
noSelector Don’t allow to start the VirtualBox manager. Trying to do so will show a window containing a proper error message.noMenuBar VM windows will not contain a menu bar.
To disable all host key combinations, open the preferences and change the host key to None.This might be useful when using VirtualBox in a kiosk mode. Furthermore, you can disallow certain actions when terminating a VM. To disallow specificactions, type:VBoxManage setextradata "VM name" GUI/RestrictedCloseActions OPTION[,OPTION...]
SaveState Don’t allow the user to save the VM state when terminating the VM.
Shutdown Don’t allow the user to shutdown the VM by sending the ACPI power-off event to the guest.PowerOff Don’t allow the user to power off the VM.
Restore Don’t allow the user to return to the last snapshot when powering off the VM.
Any combination of the above is allowed. If all options are specified, the VM cannot be shutdown at all.
For additional information on how launchd services could be configured see http:// developer.apple.com/mac/library/documentation/MacOSX/Conceptual/BPSystemStartup/ BPSystemStartup.html.
15010 Technical backgroundThe contents of this chapter are not required to use VirtualBox successfully. The following isprovided as additional information for readers who are more familiar with computer architectureand technology and wish to find out more about how VirtualBox works “under the hood”.
For simplicity, we will abbreviate this as $HOME below. Using that convention, the commonfolder for all virtual machines is $HOME/VirtualBox VMs. As an example, when you create a virtual machine called “Example VM”, you will find thatVirtualBox creates
This is the default layout if you use the “Create new virtual machine” wizard as described inchapter 1.7, Creating your first virtual machine, page 16. Once you start working with the VM,additional files will show up: you will find log files in a subfolder called Logs, and once you havetaken snapshots, they will appear in a Snapshots subfolder. For each VM, you can change thelocation of its snapsnots folder in the VM settings. You can change the default machine folder by selecting “Preferences” from the “File” menuin the VirtualBox main window. Then, in the window that pops up, click on the “General” tab.Alternatively, use VBoxManage setproperty machinefolder; see chapter 8.25, VBoxManagesetproperty, page 126.
151 10 Technical background
1. It was very difficult to move a virtual machine from one host to another because the files involved did not reside in the same folder. In addition, the virtual media of all machines were registered with a global registry in the central VirtualBox settings file ($HOME/.VirtualBox/VirtualBox.xml). To move a machine to another host, it was therefore not enough to move the XML settings file and the disk images (which were in different locations), but the hard disk entries from the global media registry XML had to be meticulously copied as well, which was close to impossible if the machine had snapshots and therefore differencing images. 2. Storing virtual disk images, which can grow very large, under the hidden .VirtualBox directory (at least on Linux and Solaris hosts) made many users wonder where their disk space had gone.
Whereas new VMs created with VirtualBox 4.0 or later will conform to the new layout, formaximum compatibility, old VMs are not converted to the new layout. Otherwise machine set-tings would be irrevocably broken if a user downgraded from 4.0 back to an older version ofVirtualBox.
152 10 Technical background
1. VBoxSVC, the VirtualBox service process which always runs in the background. This pro- cess is started automatically by the first VirtualBox client process (the GUI, VBoxManage, VBoxHeadless, the web service or others) and exits a short time after the last client exits. The service is responsible for bookkeeping, maintaining the state of all VMs, and for provid- ing communication between VirtualBox components. This communication is implemented via COM/XPCOM.
Note: When we refer to “clients” here, we mean the local clients of a particu- lar VBoxSVC server process, not clients in a network. VirtualBox employs its own client/server design to allow its processes to cooperate, but all these processes run un- der the same user account on the host operating system, and this is totally transparent to the user..
153 10 Technical background
2. The GUI process, VirtualBox, a client application based on the cross-platform Qt li- brary. When started without the --startvm option, this application acts as the VirtualBox manager, displaying the VMs and their settings. It then communicates settings and state changes to VBoxSVC and also reflects changes effected through other means, e.g., VBoxManage.
3. If the VirtualBox client application is started with the --startvm argument, it loads the VMM library which includes the actual hypervisor and then runs a virtual machine and provides the input and output for the guest.
Any VirtualBox front-end (client) will communicate with the service process and can bothcontrol and reflect the current state. For example, either the VM selector or the VM window orVBoxManage can be used to pause the running VM, and other components will always reflectthe changed state. The VirtualBox GUI application is only one of several available front ends (clients). The com-plete list shipped with VirtualBox is:
1. VirtualBox, the Qt front end implementing the manager and running VMs; 2. VBoxManage, a less user-friendly but more powerful alternative, described in chapter 8, VBoxManage, page 100. 3. VBoxSDL, a simple graphical front end based on the SDL library; see chapter 9.1, VBoxSDL, the simplified VM displayer, page 134. 4. VBoxHeadless, a VM front end which does not directly provide any video output and keyboard/mouse input, but allows redirection via VirtualBox Remote Desktop Extension; see chapter 7.1.2, VBoxHeadless, the remote desktop server, page 92. 5. vboxwebsrv, the VirtualBox web service process which allows for controlling a VirtualBox host remotely. This is described in detail in the VirtualBox Software Development Kit (SDK) reference; please see chapter 11, VirtualBox programming interfaces, page 161 for details. 6. The VirtualBox Python shell, a Python alternative to VBoxManage. This is also described in the SDK reference.
Internally, VirtualBox consists of many more or less separate components. You may encounterthese when analyzing VirtualBox internal error messages or log files. These include:
• IPRT, a portable runtime library which abstracts file access, threading, string manipulation, etc. Whenever VirtualBox accesses host operating features, it does so through this library for cross-platform portability. • VMM (Virtual Machine Monitor), the heart of the hypervisor. • EM (Execution Manager), controls execution of guest code. • REM (Recompiled Execution Monitor), provides software emulation of CPU instructions. • TRPM (Trap Manager), intercepts and processes guest traps and exceptions. • HWACCM (Hardware Acceleration Manager), provides support for VT-x and AMD-V. • PDM (Pluggable Device Manager), an abstract interface between the VMM and emulated devices which separates device implementations from VMM internals and makes it easy to add new emulated devices. Through PDM, third-party developers can add new virtual devices to VirtualBox without having to change VirtualBox itself. • PGM (Page Manager), a component controlling guest paging.
154 10 Technical background
• PATM (Patch Manager), patches guest code to improve and speed up software virtualiza- tion. • TM (Time Manager), handles timers and all aspects of time inside guests. • CFGM (Configuration Manager), provides a tree structure which holds configuration set- tings for the VM and all emulated devices. • SSM (Saved State Manager), saves and loads VM state. • VUSB (Virtual USB), a USB layer which separates emulated USB controllers from the con- trollers on the host and from USB devices; this also enables remote USB. • DBGF (Debug Facility), a built-in VM debuger. • VirtualBox emulates a number of devices to provide the hardware environment that var- ious guests need. Most of these are standard devices found in many PC compatible ma- chines and widely supported by guest operating systems. For network and storage devices in particular, there are several options for the emulated devices to access the underlying hardware. These devices are managed by PDM. • Guest Additions for various guest operating systems. This is code that is installed from within a virtual machine; see chapter 4, Guest Additions, page 53. • The “Main” component is special: it ties all the above bits together and is the only public API that VirtualBox provides. All the client processes listed above use only this API and never access the hypervisor components directly. As a result, third-party applications that use the VirtualBox Main API can rely on the fact that it is always well-tested and that all capabilities of VirtualBox are fully exposed. It is this API that is described in the VirtualBox SDK mentioned above (again, see chapter 11, VirtualBox programming interfaces, page 161).
Note: On many systems, the hardware virtualization features first need to be enabled in the BIOS before VirtualBox can use them.
155 10 Technical background
• As opposed to other virtualization software, for many usage scenarios, VirtualBox does not require hardware virtualization features to be present. Through sophisticated techniques, VirtualBox virtualizes many guest operating systems entirely in software. This means that you can run virtual machines even on older processors which do not support hardware virtualization.
Even though VirtualBox does not always require hardware virtualization, enabling it is requiredin the following scenarios:
• Certain rare guest operating systems like OS/2 make use of very esoteric processor instruc- tions that are not supported with our software virtualization. For virtual machines that are configured to contain such an operating system, hardware virtualization is enabled automatically.
•.)
156 10 Technical background
and run that code natively on the processor. The problems mostly lie in how to intercept whatthe guest’s kernel does. There are several possible solutions to these problems. One approach is full software emu-lation, usually involving recompilation. That is, all code to be run by the guest is analyzed,transformed into a form which will not allow the guest to either modify or see the true state ofthe CPU, and only then executed. This process is obviously highly complex and costly in termsof performance. (VirtualBox contains a recompiler based on QEMU which can be used for puresoftware emulation, but the recompiler is only activated in special situations, described below.) Another possible solution is paravirtualization, in which only specially modified guest OSesare allowed to run. This way, most of the hardware access is abstracted and any functions whichwould normally access the hardware or privileged CPU state are passed on to the hypervisorinstead. Paravirtualization can achieve good functionality and performance on standard x86CPUs, but it can only work if the guest OS can actually be modified, which is obviously notalways the case. VirtualBox chooses a different approach. When starting a virtual machine, through its ring-0support kernel driver, VirtualBox has set up the host system so that it can run most of the guestcode natively, but it has inserted itself at the “bottom” of the picture. It can then assume controlwhen needed – if a privileged instruction is executed, the guest traps (in particular becausean I/O register was accessed and a device needs to be virtualized) or external interrupts occur.VirtualBox may then handle this and either route a request to a virtual device or possibly delegatehandling such things to the guest or host OS. In guest context, VirtualBox can therefore be inone of three states:
• Guest ring 3 code is run unmodified, at full speed, as much as possible. The number of faults will generally be low (unless the guest allows port I/O from ring 3, something we cannot do as we don’t want the guest to be able to access real ports). This is also referred to as “raw mode”, as the guest ring-3 code runs unmodified.
•.
• The hypervisor (VMM) can be active. Every time a fault occurs, VirtualBox looks at the offending instruction and can relegate it to a virtual device or the host OS or the guest OS or run it in the recompiler. In particular, the recompiler is used when guest code disables interrupts and VirtualBox cannot figure out when they will be switched back on (in these situations, VirtualBox actu- ally analyzes the guest code using its own disassembler). Also, certain privileged instruc- tions such as LIDT need to be handled specially. Finally, any real-mode or protected-mode code (e.g. BIOS code, a DOS guest, or any operating system startup) is run in the recom- piler entirely.
Unfortunately this only works to a degree. Among others, the following situations requirespecial handling:
1. Running ring 0 code in ring 1 causes a lot of additional instruction faults, as ring 1 is not allowed to execute any privileged instructions (of which guest’s ring-0 contains plenty). With each of these faults, the VMM must step in and emulate the code to achieve the desired behavior. While this works, emulating thousands of these faults is very expensive and severely hurts the performance of the virtualized guest.
2. There are certain flaws in the implementation of ring 1 in the x86 architecture that were never fixed. Certain instructions that should trap in ring 1 don’t. This affect for example the
157 10 Technical background
To fix these performance and security issues, VirtualBox contains a Code Scanning and AnalysisManager (CSAM), which disassembles guest code, and the Patch Manager (PATM), which canreplace it at runtime. Before executing ring 0 code, CSAM scans it recursively to discover problematic instructions.PATM then performs in-situ patching, i.e. it replaces the instruction with a jump to hypervisormemory where an integrated code generator has placed a more suitable implementation. Inreality, this is a very complex task as there are lots of odd situations to be discovered and handledcorrectly. So, with its current complexity, one could argue that PATM is an advanced in-siturecompiler. In addition, every time a fault occurs, VirtualBox analyzes the offending code to determine if itis possible to patch it in order to prevent it from causing more faults in the future. This approachworks well in practice and dramatically improves software virtualization performance.
• In root mode, the CPU operates much like older generations of processors without VT-x support. There are four privilege levels (“rings”), and the same instruction set is supported, with the addition of several virtualization specific instruction. Root mode is what a host operating system without virtualization uses, and it is also used by a hypervisor when virtualization is active. • In non-root mode, CPU operation is significantly different. There are still four privilege rings and the same instruction set, but a new structure called VMCS (Virtual Machine Con- trol Structure) now controls the CPU operation and determines how certain instructions behave. Non-root mode is where guest systems run.
Switching from root mode to non-root mode is called “VM entry”, the switch back is “VM exit”.The VMCS includes a guest and host state area which is saved/restored at VM entry and exit.Most importantly, the VMCS controls which guest operations will cause VM exits.
158 10 Technical background
The VMCS provides fairly fine-grained control over what the guests can and can’t do. Forexample, a hypervisor can allow a guest to write certain bits in shadowed control registers, butnot others. This enables efficient virtualization in cases where guests can be allowed to writecontrol bits without disrupting the hypervisor, while preventing them from altering control bitsover which the hypervisor needs to retain full control. The VMCS also provides control overinterrupt delivery and exceptions. Whenever an instruction or event causes a VM exit, the VMCS contains information aboutthe exit reason, often with accompanying detail. For example, if a write to the CR0 registercauses an exit, the offending instruction is recorded, along with the fact that a write access toa control register caused the exit, and information about source and destination register. Thusthe hypervisor can efficiently handle the condition without needing advanced techniques such asCSAM and PATM described above. VT-x inherently avoids several of the problems which software virtualization faces. The guesthas its own completely separate address space not shared with the hypervisor, which eliminatespotential clashes. Additionally, guest OS kernel code runs at privilege ring 0 in VMX non-rootmode, obviating the problems by running ring 0 code at less privileged levels. For example theSYSENTER instruction can transition to ring 0 without causing problems. Naturally, even at ring0 in VMX non-root mode, any I/O access by guest code still causes a VM exit, allowing for deviceemulation. The biggest difference between VT-x and AMD-V is that AMD-V provides a more completevirtualization environment. VT-x requires the VMX non-root code to run with paging enabled,which precludes hardware virtualization of real-mode code and non-paged protected-mode soft-ware. This typically only includes firmware and OS loaders, but nevertheless complicates VT-xhypervisor implementation. AMD-V does not have this restriction. Of course hardware virtualization is not perfect. Compared to software virtualization, theoverhead of VM exits is relatively high. This causes problems for devices whose emulation re-quires high number of traps. One example is the VGA device in 16-color modes, where not onlyevery I/O port access but also every access to the framebuffer memory must be trapped.
159 10 Technical background
enable this feature for a VM, you need to use the VBoxManage modifyvm --largepages command; see chapter 8.7, VBoxManage modifyvm, page 110.
• On Intel CPUs, another hardware feature called “Virtual Processor Identifiers” (VPIDs) can greatly accelerate context switching by reducing the need for expensive flushing of the processor’s Translation Lookaside Buffers (TLBs). To enable these features for a VM, you need to use the VBoxManage modifyvm --vtxvpids and --largepages commands; see chapter 8.7, VBoxManage modifyvm, page 110.
16011 VirtualBox programming interfacesVirtualBox comes with comprehensive support for third-party developers. The so-called “MainAPI” of VirtualBox exposes the entire feature set of the virtualization engine. It is completelydocumented and available to anyone who wishes to control VirtualBox programmatically. The Main API is made available to C++ clients through COM (on Windows hosts) or XPCOM(on other hosts). Bridges also exist for SOAP, Java and Python. All programming information (documentation, reference information, header and other in-terface files as well as samples) have been split out to a separate Software Development Kit(SDK), which is available for download from. In particular, theSDK comes with a “Programming Guide and Reference” in PDF format, which contains, amongother things, the information that was previously in this chapter of the User Manual.
16112 TroubleshootingThis chapter provides answers to commonly asked questions. In order to improve your userexperience with VirtualBox, it is recommended to read this section to learn more about commonpitfalls and get recommendations on how to use the product.
162 12 Troubleshooting
When starting a VM, the configuration file of the last run will be renamed to .1, up to .3.Sometimes when there is a problem, it is useful to have a look at the logs. Also when requestingsupport for VirtualBox, supplying the corresponding log file is mandatory. For convenience, for each virtual machine, the VirtualBox main window can show these logs ina window. To access it, select a virtual machine from the list on the left and select “Show logs...“from the “Machine” window. The release log file (VBox.log) contains a wealth of diagnostic information, such as Host OStype and version, VirtualBox version and build (32-bit or 64-bit), a complete dump of the guest’sconfiguration (CFGM), detailed information about the host CPU type and supported features,whether hardware virtualization is enabled, information about VT-x/AMD-V setup, state tran-sitions (creating, running, paused, stopping, etc.), guest BIOS messages, Guest Additions mes-sages, device-specific log entries and, at the end of execution, final guest state and condensedstatistics. In case of crashes, it is very important to collect crash dumps. This is true for both host andguest crashes. For information about enabling core dumps on Linux, Solaris, and OS X systems,refer to the core dump article on the VirtualBox website.1 You can also use VBoxManage debugvm to create a dump of a complete virtual machine; seechapter 8.30, VBoxManage debugvm, page 130. For network related problems, it is often helpful to capture a trace of network traffic. If thetraffic is routed through an adapter on the host, it is possible to use Wireshark or a similar toolto capture the traffic there. However, this often also includes a lot of traffic unrelated to the VM. VirtualBox provides an ability to capture network traffic only on a specific VM’s networkadapter. Refer to the network tracing article on the VirtualBox website2 for information onenabling this capture. The trace files created by VirtualBox are in .pcap format and can be easilyanalyzed with Wireshark.
Warning: VirtualBox, but it is disabledby default because the average user will have little use for it. There are two ways to access thedebugger:
1. 2.
163 12 Troubleshooting
• Start the VM directly using VirtualBox --startvm, with an additional --dbg, --debug, or --debug-command-line argument. See the VirtualBox usage help for details.
A new ’Debug’ menu entry will be added to the VirtualBox application. This menu allows theuser to open the debugger console. The VM debugger command syntax is loosely modeled on Microsoft and IBM debuggers usedon DOS, OS/2 and Windows. Users familiar with symdeb, CodeView, or the OS/2 kernel debug-ger will find the VirtualBox VM debugger familiar. The most important command is help. This will print brief usage help for all debugger com-mands. The set of commands supported by the VM debugger changes frequently and the helpcommand is always up-to-date. A brief summary of frequently used commands follows:
• bc – clear a breakpoint • writecore – writes a VM core file to disk, refer chapter 12.1.4, VM core format, page 165
164 12 Troubleshooting
The output of the info commands generally requires in-depth knowledge of the emulated de-vice and/or VirtualBox VMM internals. However, when used properly, the information providedcan be invaluable.
165 12 Troubleshooting
The memory descriptors contain physical addresses relative to the guest and not virtual ad-dresses. Regions of memory such as MMIO regions are not included in the core file. The relevant data structures and definitions can be found in the VirtualBox sources underthe following header files: include/VBox/dbgfcorefmt.h, include/VBox/cpumctx.h andsrc/VBox/Runtime/include/internal/ldrELFCommon.h. The VM core file can be inspected using elfdump and GNU readelf or other similar utilities.
12.2 General12.2.1 Guest shows IDE/SATA errors for file-based images on slow host file systemOccasionally, some host file systems provide very poor writing performance and as a consequencecause the guest to time out IDE/SATA commands. This is normal behavior and should normallycause no real problems, as the guest should repeat commands that have timed out. Howeversome guests (e.g. some Linux versions) have severe problems if a write to an image file takeslonger than about 15 seconds. Some file systems however require more than a minute to com-plete a single write, if the host cache contains a large amount of data that needs to be written. The symptom for this problem is that the guest can no longer access its files during large writeor copying operations, usually leading to an immediate hang of the guest. In order to work around this problem (the true fix is to use a faster file system that doesn’texhibit such unacceptable write performance), it is possible to flush the image file after a cer-tain amount of data has been written. This interval is normally infinite, but can be configuredindividually for each disk of a VM. For IDE disks use the following command:VBoxManage setextradata "VM name" "VBoxInternal/Devices/piix3ide/0/LUN#[x]/Config/FlushInterval" [b]
The value [x] that selects the disk for IDE is 0 for the master device on the first channel, 1 forthe slave device on the first channel, 2 for the master device on the second channel or 3 for themaster device on the second channel. For SATA use values between 0 and 29. Only disks supportthis configuration option; it must not be set for CD/DVD drives. The unit of the interval [b] is the number of bytes written since the last flush. The value for itmust be selected so that the occasional long write delays do not occur. Since the proper flush in-terval depends on the performance of the host and the host filesystem, finding the optimal valuethat makes the problem disappear requires some experimentation. Values between 1000000 and10000000 (1 to 10 megabytes) are a good starting point. Decreasing the interval both decreasesthe probability of the problem and the write performance of the guest. Setting the value unnec-essarily low will cost performance without providing any benefits. An interval of 1 will cause a
166 12 Troubleshooting
flush for each write operation and should solve the problem in any case, but has a severe writeperformance penalty. Providing a value of 0 for [b] is treated as an infinite flush interval, effectively disabling thisworkaround. Removing the extra data key by specifying no value for [b] has the same effect.
The value [x] that selects the disk is 0 for the master device on the first channel, 1 for the slavedevice on the first channel, 2 for the master device on the second channel or 3 for the masterdevice on the second channel. To enable flushing for SATA disks, issue the following command:VBoxManage setextradata "VM name" "VBoxInternal/Devices/ahci/0/LUN#[x]/Config/IgnoreFlush" 0
The value [x] that selects the disk can be a value between 0 and 29. Note that this doesn’t affect the flushes performed according to the configuration described inchapter 12.2.1, Guest shows IDE/SATA errors for file-based images on slow host file system, page166. Restoring the default of ignoring flush commands is possible by setting the value to 1 or byremoving the key.
It will list the required OpenGL extensions one by one and will show you which one failed thetest. This usually means that you are running an outdated or misconfigured OpenGL driver onyour host. It can also mean that your video chip is lacking required functionality.
167 12 Troubleshooting
This sets the delay to one millisecond. In case this doesn’t help, increase it to a value between1 and 5 milliseconds. Please note that this slows down disk performance. After installation, youshould be able to remove the key (or set it to 0).3 See.
168 12 Troubleshooting
169 12 Troubleshooting
• The Linux kernel version 2.6.18 (and some 2.6.17 versions) introduced a race condition that can cause boot crashes in VirtualBox. Please use a kernel version 2.6.19 or later. • (see chapter 3.4, System settings, page 43), or upgrade the guest to a newer kernel.4
when your X11 user session is started if you are using a common desktop environment (Gnome,KDE and others). If a particular desktop service is not working correctly, it is worth checkingwhether the process which should provide it is running. The VBoxClient processes create files in the user’s home directory with names of the form.vboxclient-*.pid when they are running in order to prevent a given service from beingstarted twice. It can happen due to misconfiguration that these files are created owned by rootand not deleted when the services are stopped, which will prevent them from being started infuture sessions. If the services cannot be started, you may wish to check whether these files stillexist.
170 12 Troubleshooting
it requests access to the COM server and Windows automatically starts the process. Note that itshould never be started by the end user. When the last process disconnects from the COM server, it will terminate itself after someseconds. The VirtualBox configuration (XML files) is maintained and owned by the COM serverand the files are locked whenever the server runs. In some cases - such as when a virtual machine is terminated unexpectedly - the COM serverwill not notice that the client is disconnected and stay active for a longer period (10 minutes orso) keeping the configuration files locked. In other rare cases the COM server might experiencean internal error and subsequently other processes fail to initialize it. In these situations, it isrecommended to use the Windows task manager to kill the process VBoxSVC.exe.
Certain applications may disable this key against Microsoft’s advice. If it is set to 0, change it to1 and reboot your system. VirtualBox relies on Windows notifying it of media changes.
orHKEY_LOCAL_MACHINE\Software\Microsoft\Terminal Server Client\Min Send Interval
171 12 Troubleshooting
set VBOX_DISABLE_HOST_DISK_CACHE=1VirtualBox
While this will decrease guest disk performance (especially writes), it does not affect the per-formance of other applications running on the host.
• The maximum allowed filter count was reached on the host. In this case, the MSI log would mention the 0x8004a029 error code returned on NetFlt network component install: VBoxNetCfgWinInstallComponent: Install failed, hr (0x8004a029)
You can try to increase the maximum filter count in the Windows registry at the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters
The maximum number allowed is 14. After a reboot, try to re-install VirtualBox. • The INF cache is corrupt. In this case, the install log (%windir%\inf\setupapi.log on XP or %windir%\inf\setupapi.dev.log on Vista or later) would typically men- tion the failure to find a suitable driver package for either the sun_VBoxNetFlt or sun_VBoxNetFltmp components. The solution then is to uninstall VirtualBox, remove the INF cache (%windir%\inf\INFCACHE.1), reboot and try to re-install VirtualBox
172 12 Troubleshooting checking ’
On modern Linux distributions, VirtualBox uses the hardware abstraction layer (hal) to locateCD and DVD hardware.
173 12 Troubleshootingis part of the udev configuration file /etc/udev/rules.d/50-udev.rules. As this distributionhas no user group called usb, you may e.g. use the vboxusers group which was created bythe VirtualBox installer. Since group numbers are allocated dynamically, the following exampleuses 85 as a placeholder. Modify the line containing (a linebreak has been inserted to improveread distribu-tion has no group usb, it is also the easiest solution to allow all members of the group vboxusersto access the USB subsystem. Modify the linedomount usbfs usbdevfs /proc/bus/usb -onoexec,nosuid,nodev
so that it containsdom.
174 12 Troubleshooting
to /etc/system where xxxx bytes is the amount of memory usable for the ZFS cache.
Note: This restriction applies only to 32-bit Solaris hosts, 64-bit hosts are not affected!
For existing Solaris 10 installs, an additional swap image needs to be mounted and used asswap. Hence if you have 1 GB swap and 8 GB of physical memory, you require to add 7 GB moreswap. This can be done as follows: For ZFS (as root user):zfs create -V 8gb /_<ZFS volume>_/swapswap -a /dev/zvol/dsk/_<ZFS volume>_/swap
175 12 Troubleshooting
17613 Security considerations13.1 Potentially insecure operationsThe following features of VirtualBox can present security problems: • Enabling 3D graphics via the Guest Additions exposes the host to additional security risks; see chapter 4.4.1, Hardware 3D acceleration (OpenGL and Direct3D 8/9), page 65. • When teleporting a machine, the data stream through which the machine’s memory con- tents are transferred from one host to another is not encrypted. A third party with access to the network through which the data is transferred could therefore intercept that data. • When using the VirtualBox web service to control a VirtualBox host remotely, connections to the web service (through which the API calls are transferred via SOAP XML) are not encrypted, but use plain HTTP. For details about the web service, please see chapter 11, VirtualBox programming interfaces, page 161.
13.2 AuthenticationThe following components of VirtualBox can use passwords for authentication: • When using the VirtualBox extension pack provided by Oracle for VRDP remote desktop support, you can optionally use various methods to configure RDP authentication. See chapter 7.1.5, RDP authentication, page 95 for details. • When using teleporting, passwords can optionally be used to protect a machine waiting to be teleported from unauthorized access. Note however that these passwords are stored unencrypted in the machine configuration XML and therefore potentially readable on the host. See chapter 7.2, Teleporting, page 98 and chapter 8.7.5, Teleporting settings, page 115. • When using remote iSCSI storage and the storage server requires authentication, a pass- word can optionally be supplied with the VBoxManage storageattach command. Note however that this is stored unencrypted in the machine configuration and is therefore po- tentially readable on the host. See chapter 5.10, iSCSI servers, page 83 and chapter 8.16, VBoxManage storageattach, page 120. • When using the VirtualBox web service to control a VirtualBox host remotely, connections to the web service are authenticated in various ways. This is described in detail in the VirtualBox Software Development Kit (SDK) reference; please see chapter 11, VirtualBox programming interfaces, page 161.
13.3 EncryptionThe following components of VirtualBox use encryption to protect sensitive data: • When using the VirtualBox extension pack provided by Oracle for VRDP remote desktop support, RDP data can optionally be encrypted. See chapter 7.1.6, RDP encryption, page 96 for details.
17714 Known limitationsThis sections describes known problems with VirtualBox 4.0.0. Unless marked otherwise, theseissues are planned to be fixed in later releases. • The following Guest SMP (multiprocessor) limitations exist: – Poor performance with 32-bit guests on AMD CPUs. This affects mainly Windows and Solaris guests, but possibly also some Linux kernel revisions. Partially solved in 3.0.6 for 32 bits Windows NT, 2000, XP and 2003 guests. Requires 3.0.6 or higher Guest Additions to be installed. – Poor performance with 32-bit guests on certain Intel CPU models that do not include virtual APIC hardware optimization support. This affects mainly Windows and Solaris guests, but possibly also some Linux kernel revisions. Partially solved in 3.0.12 for 32 bits Windows NT, 2000, XP and 2003 guests. Requires 3.0.12 or higher Guest Additions to be installed. • 64-bit guests on some 32-bit host systems with VT-x can cause instabilities to your system. If you experience this, do not attempt to execute 64-bit guests. Refer to the VirtualBox user forum for additional information. • For Direct3D support in Windows guests to work, the Guest Additions must be installed in Windows “safe mode”. Press F8 when the Windows guest is booting and select “Safe mode”, then install the Guest Additions. Otherwise Windows’ file protection mechanism will interfere with the replacement DLLs installed by VirtualBox and keep restoring the original Windows system DLLs. • Guest control. On Windows guests, a process lauched via the guest control execute support will not be able to display a graphical user interface unless the user account under which it is running is currently logged in and has a desktop session. Also, to use accounts without or with an empty password, the guest’s group policy must be changed. To do so, open the group policy editor on the command line by typ- ing gpedit.msc, open the key Computer Configuration\Windows Settings\Security Set- tings\Local Policies\Security Options and change the value of Accounts: Limit local account use of blank passwords to console logon only to Disabled. • Compacting virtual disk images is limited to VDI files. The VBoxManage modifyhd -compact command is currently only implemented for VDI files. At the moment the only way to optimize the size of a virtual disk images in other formats (VMDK, VHD) is to clone the image and then use the cloned image in the VM configuration. • OVF import/export: – OVF localization (multiple languages in one OVF file) is not yet supported. – Some OVF sections like StartupSection, DeploymentOptionSection and InstallSection are ignored. – OVF environment documents, including their property sections and appliance config- uration with ISO images, are not yet supported. – Remote files via HTTP or other mechanisms are not yet supported. • Neither scale mode nor seamless mode work correctly with guests using OpenGL 3D features (such as with compiz-enabled window managers).
178 14 Known limitations
• Solaris hosts: – There is no support for USB devices connected to Solaris 10 hosts. – USB support on Solaris hosts requires kernel version snv_124 or higher. Webcams and other isochronous devices are known to have poor performance. – No ACPI information (battery status, power source) is reported to the guest. – No support for using wireless adapters with bridged networking.
• Guest Additions for OS/2. Shared folders are not yet supported with OS/2 guests. In ad- dition, seamless windows and automatic guest resizing will probably never be implemented due to inherent limitations of the OS/2 graphics system.
17915 Change logThis section summarizes the changes between VirtualBox versions. Note that this change log isnot exhaustive; not all changes are listed. VirtualBox version numbers consist of three numbers separated by dots where the first andsecond number represent the major version and the 3rd number the minor version. Minor versionnumbers of official releases are always even. An odd minor version number represents an internaldevelopment or test build. In addition, each build contains a revision number.
• Reorganization of VirtualBox into a base package and Extension Packs; see chapter 1.5, Installing VirtualBox and extension packs, page 14 • New settings/disk file layout for VM portability; see chapter 10.1, Where VirtualBox stores its files, page 151 • Major rework of the GUI (now called “VirtualBox Manager”): – Redesigned user interface with guest window preview (also for screenshots) – New “scale” display mode with scaled guest display; see chapter 1.8.5, Resizing the machine’s window, page 21 –) • VMM: support more than 1.5/2 GB guest RAM on 32-bit hosts
• Improvements to OVF support (see chapter 1.12, Importing and exporting virtual machines, page 26): – Open Virtualization Format Archive (OVA) support – Significant performance improvements during export and import – Creation of the manifest file on export is optional now – Imported disks can have formats other than VMDK • Resource control: added support for limiting a VM’s CPU time and IO bandwidth; see chapter 5.8, Limiting bandwidth for disk images, page 81
180 15 Change log
• Storage: support asynchronous I/O for iSCSI, VMDK, VHD and Parallels images
• Storage: support for resizing VDI and VHD images; see chapter 8.21, VBoxManage modi- fyhd, page 124. • Guest Additions: support for multiple virtual screens in Linux and Solaris guests using X.Org server 1.3 and later • Language bindings: uniform Java bindings for both local (COM/XPCOM) and remote (SOAP) invocation APIs
• VMM: Enable large page support by default on 64-bit hosts (applies to nested paging only)
• VMM: fixed guru meditation when running Minix (VT-x only; bug #6557) • VMM: fixed crash under certain circumstances (Linux hosts only, non VT-x/AMD-V mode only; bugs #4529 and #7819) • GUI: add configuration dialog for port forwarding in NAT mode (bug #1657)
• Bridged networking: improved throughput by filtering out outgoing packets intended for the host before they reach the physical network (Linux hosts only; bug #7792) • 3D support: allow use of CR_SYSTEM_GL_PATH again (bug #6864) • 3D support: fixed various clipping/visibility issues (bugs #5659, #5794, #5848, #6018, #6187, #6570) • 3D support: guest application stack corruption when using glGetVertexAttrib[ifd]v (bug #7395) • 3D support: fixed OpenGL support for libMesa 7.9
• Floppy: support readonly image files, taking this as the criteria for making the medium readonly (bug #5651) • Audio: fixed memory corruption during playback under rare circumstances
181 15 Change log
• Audio: the DirectSound backend now allows VMs to be audible when another DirectSound application is active, including another VM (bug #5578) • EFI: support for SATA disks and CDROMs • BIOS: reduce the stack usage of the VESA BIOS function #4F01 (Quake fix) • OVF/OVA: fixed export of VMs with iSCSI disks • Storage: Apple DMG image support for the virtual CD/DVD (bug #6760) • Linux host USB support: introduced a less invasive way of accessing raw USB devices (bugs #1093, #5345, #7759) • Linux hosts: support recent Linux kernels with CONFIG_DEBUG_SET_MODULE_RONX set • Guest Additions: Shared Folders now can be marked as being auto-mounted on Windows, Linux and Solaris guests • Linux Additions: Shared Folders now support symbolic links (bug #818) • Linux Additions: combined 32-bit and 64-bit additions into one file • Windows Additions: automatic logon on Windows Vista/Windows 7 is now able to handle renamed user accounts; added various bugfixes
• VMM: fixed rare host crash when running 64-bit guests on 32-bit hosts (bug #7577) • VMM: fixed host reboots under rare circumstances due to NMIs triggered by active perfor- mance counters (Linux hosts in non-VT-x/AMD-V mode only; bug #4529) • VMM: fixed out of memory guru meditation for large memory guests (bug #7586) • VMM: fixed a guru meditation related to large pages • VMM: use new VT-x feature to keep the guest from hogging the CPU • Snapshots: implemented deleting the last remaining snapshot while the VM is running • GUI: perform the checks for exceeding the size limit of the host file system and for broken asynchronous I/O on older Linux kernels with ext4 / xfs file systems not only when starting the VM from scratch but also when starting from a saved state • NAT: fixed memory leak (3.2.0 regression; bugs #6918, #7353) • NAT: fixed Linux NFS root issue (bugs #7299) • Networking: fixed VM reset handling in e1000 • VRDP: fixed rare crash in multimonitor configuration • Display: fixed occasional guest resize crash • Mouse: don’t send relative mouse events together with absolute mouse events (3.2.10 regression; bug #7571) • Keyboard: fixes for the USB keyboard emulation; fixes for Koran keyboards
182 15 Change log
• Serial: don’t hang if the host device would block during open (bugs #5756, #5380)
• Serial: fixed modem status lines (Linux hosts only; bug #812) • Graphics: Horizontal resolutions are no longer restricted to a multiple of 8 pixels (bug #2047; requires Guest Additions update). • USB: fixed a crash with older Linux kernels and non-ASCII characters in device strings (Linux hosts only; bug #6983, #7158, #7733; version 3.2.8 contained an incomplete fix)
• USB: fixed a crash under rare circumstances (bug #7409; Windows hosts only) • “iSCSI: respond to NOP-In requests from the target immediately to avoid being discon- nected if the guest is idle • 3D support: fixed a crash under certain circumstances (bug #7659)
• Windows hosts: another fix for BSODs under certain circumstances in VBoxNetFlt.sys (bug #7601) • Solaris hosts: fixed host USB DVD drive detection • Mac OS X hosts: fixed swapped keys for certain ISO keyboard types (bug #2996)
• Linux hosts: added link state handling for TAP devices needed for proper operation with bridged networking on kernels 2.6.36 and above (bug #7649) • Linux hosts/guests: Linux 2.6.37 fixes • Linux Additions: properly compile the vboxvideo module if DKMS is not installed (bug #7572)
• Linux Additions: fixed a memory leak when accessing non-existing files on a Shared Folders (bug #7705) • Windows Additions: skip none-mapped user accounts when enumerating user accounts for VM information
• VMM: V8086 mode fix for legacy DOS/Windows guests with EMM386 (3.2.8 regression) • VMM: stability fix (bug #7342) • VMM: fixed a Guru meditation related to large pages (bug #7300) • VMM: fixed support for large pages on Linux hosts
• VMM: fixed a Guru meditation for large memory 64-bit guests on 32-bit hosts with nested paging (bug #7544) • VMM: performance improvements for VMs with more than 2GB RAM (bug #6928)
183 15 Change log
• GUI: fixed host key handling if the host key is set to Left Alt (Linux/Solaris hosts only; 3.2.0 regression; bug #6758)• GUI: the VM can be minimized from the mini toolbar (bug #4952)• GUI: handle Ctrl+Break properly on X11 hosts (3.2.0 regression; bug #6122)• GUI: fixed the case where the user aborted the media selector for selecting the boot hard disk from the VM wizard• GUI: added a check for Linux kernels 2.6.36 or later which are known to have the asyn- chronous I/O bug on ext4 / xfs file systems fixed (Linux hosts only)• OpenSolaris guests: use SATA controller by default• Storage: fixed I/O errors in the guest after compacting VDI images (3.2.6 regression; bug #7294)• Storage: automatically repair base disk images with non-zero parent UUID which made them inaccessible (bug #7289)• Storage: fixed corrupted images if a merge operation was canceled• IDE: added ATAPI passthrough support for audio CDs• SATA: fixed a potential hang during boot of recent Solaris guests• SATA: handle out of disk space and similar conditions better• iSCSI: fixed sporadic hangs when closing the connection• VGA: fixed missing redraw with multiple screens under certain circumstances (bug #7291)• VGA: serveral small fixes for legacy VGA graphics modes• Bridged networking: fixed occasional host freeze during VM shutdown (Linux hosts only)• NAT: don’t check for the existence of the TFTP prefix when delivering a file via bootp (bug #7384)• NAT: fixed resolving of names at the host resolver (bug #7138)• NAT: under rare conditions the NAT engine consumed 100% CPU load (non-Windows hosts only)• VRDP: fixed memory leak under certain circumstances (bug #5966)• VRDP: fixed missing redraws with Windows guests under certain circumstances• USB: properly discard blocking outstanding bulk URBs, fixes some printers• USB: Blackberry fix (bug #6465)• VBoxHeadless: fixed event queue processing problems which led to hangs if the VM could not be started successfully• VBoxManage: don’t crash if parameters with invalid characters are passed (bug #7388)• VBoxManage: clonehd: fixed a bug where the command aborted with an error message under rare circumstances• VBoxManage metrics: made it work for directly started VMs again (3.2.8 regression; bug #7482)
184 15 Change log
185 15 Change log
• VMM: properly terminate the VM with an error if the guest is trying to switch to the PAE mode but PAE is disabled in the VM settings • GUI: switch to native file dialogs (Windows hosts only; bug 5459)
• GUI: don’t use native file dialogs on KDE hosts (Linux hosts only; bug #6809) • 3D support: fixed GL_EXT_texture_sRGB support • PXE: fixed ZENworks PXE boot regression
• OVF: fixed slower export and larger images under certain circumstances (3.2.6 regression; bug #7073) • USB: properly signal an interrupt if the port suspend status changes • USB: respect the remote-only filter
• USB: avoid VM hang when changing the configuration of certain devices (Windows hosts only) • USB: fix a crash with older Linux kernels and non-ASCII characters in device strings (Linux hosts only; bug #6983)
• Bridged networking: fixed performance issue with GRO enabled on bridged device (bug #7059) • Hostonly networking: fixed performance issue (3.2.6 regression; bug #7081) • Hard disks: fix auto-reset of immutable disk at VM startup (bug #6832)
• BusLogic: several fixes for Windows NT/2000 and SCO OpenServer guests • LsiLogic: fixed I/O errors under rare circumstances • Sharing disks: support for attaching one disk to several VMs without external tools and tricks
• Shared Folders: several fixes and performance enhancements for Solaris guests (bugs #4154 and #6512) • Solaris Installer: added support for remote installations
186 15 Change log
• Guest Properties API: correctly support enumerating the properties of a running VM with an empty “patterns” field (bug #7171) • Guest properties: properly delete transient properties on shutdown • RDP video redirection performance improvements and stability fixes • Settings: silently fix host audio driver when reading machine XML settings files or OVF written by VirtualBox on a different host OS, for example convert DirectSound to PulseAu- dio (bug #7209) • Settings: properly store the NAT network setting in XML settings file version 1.10 and later (bug #6176) • VBoxManage: handle differencing images with parent UUID correctly in subcommand openmedium disk (bug #6751) • Web service: enabled HTTP keepalive for much better performance • Web service: added timestamps to logging output • Web service: treat 8-bit strings as UTF-8 not ASCII • X11 Additions: fix for Xorg 6.8 guests (e.g. RHEL4)
• VMM: fixed host crash when running 64-bit guests on 32-bit hosts with certain Intel CPUs (VT-x only; bug #6166) • VMM: allow 64-bit SMP guests on 32-bit hosts (VT-x and AMD-V only; does not apply to Mac OS X, which already supports it) • VMM: fixed Guru mediation if guests with more than 2GB are booted with VT-x/AMD-V disabled (bug #5740) • VMM: fixed TR limit trashing (VT-x and 64-bit host only; bug #7052) • Page Fusion: several bug fixes for SMP guests (including bug #6964) • Teleportation: several fixes and improvements • Mac OS X server guests: compatibility fix • EFI: fixed memory detection for guests with 2GB or more RAM assigned • GUI: added a workaround for a Linux kernel bug which affecting asynchronous I/O on ext4 / xfs file systems (Linux hosts only) • GUI: added setting for multiple VRDP connections; useful if multiple screens are enabled • GUI: another fix for the keyboard capturing bug under metacity (bug #6727) • GUI: fixed quit dialog when used in seamless or fullscreen mode (Mac OS X hosts only; bug #6938) • GUI: handle the extra key on the Brazilian keyboard on X11 hosts again (bug #7022). • 2D Video acceleration: fixed crashes when leaving the fullscreen mode (bug #6768)
187 15 Change log
188 15 Change log
• GUI: fixed superfluous resize-event on powering-on VM for X11 (improvement for the 3.2.2 fix) • GUI: fixed keyboard capturing bug under metacity (bug #6727) • Host-only/bridged networking: fixed guest-to-guest communication over wireless (3.2.0 regression; bug #6855) • Storage: fixed a potential guest disk corruption with growing images (3.2.0 regression) • Page Fusion: fixed shared module detection for Win64 guests • 3D support: allow use of CR_SYSTEM_GL_PATH again (bug #6864) • 3D support: fixed a host assertion for some multi-threaded guest applications (bug #5236) • 3D support: fixed host crashes with nVIDIA drivers on WDDM startup • OVF: fixed import of OVFs with a VM description (annotation) (3.2.2 regression; bug #6914) • VRDP: fixed issues with secondary monitors (bug #6759)
• VMM: fixed rare invalid guest state guru meditation (VT-x only) • VMM: fixed poor performance with nested paging and unrestricted guest execution (VT-x only; bug #6716) • VMM: fixed occasional guru meditation during Windows 7 bootup (bug #6728) • GUI: keep the status for remote control in sync with the actual state • GUI: don’t exit after a successful refresh of an invalid VM configuration • GUI: fixed keyboard capturing bug under metacity (bug #6727) • GUI: fixed crash during VM termination if a modal dialog is open • GUI: default controllers names of New VM Wizard are synchronized with VM settings
189 15 Change log
190 15 Change log
• Following the acquisition of Sun Microsystems by Oracle Corporation, the product is now called “Oracle VM VirtualBox” and all references were changed without impacting compat- ibility • Experimental support for Mac OS X Server guests (see chapter 3.1.1, Mac OS X Server guests, page 40)
• Memory ballooning to dynamically in- or decrease the amount of RAM used by a VM (64-bit hosts only) (see chapter 4.8.1, Memory ballooning, page 70) • Page Fusion automatically de-duplicates RAM when running similar VMs thereby increas- ing capacity. Currently supported for Windows guests on 64-bit hosts (see chapter 4.8.2, Page Fusion, page 70) • CPU hot-plugging for Linux (hot-add and hot-remove) and certain Windows guests (hot- add only) (see chapter 9.4, CPU hot-plugging, page 139) • New Hypervisor features: with both VT-x/AMD-V on 64-bit hosts, using large pages can improve performance (see chapter 10.6, Nested paging and VPIDs, page 159); also, on VT- x, unrestricted guest execution is now supported (if nested paging is enabled with VT-x, real mode and protected mode without paging code runs faster, which mainly speeds up guest OS booting) • Support for deleting snapshots while the VM is running
• Support for multi-monitor guest setups in the GUI for Windows guests (see chapter 3.5, Display settings, page 45) • USB tablet/keyboard emulation for improved user experience if no Guest Additions are available (see chapter 3.4.1, “Motherboard” tab, page 43) • LsiLogic SAS controller emulation (see chapter 5.1, Hard disk controllers: IDE, SATA (AHCI), SCSI, SAS, page 72) • RDP video acceleration (see chapter 7.1.9, VRDP video redirection, page 97) • NAT engine configuration via API and VBoxManage • Use of host I/O cache is now configurable (see chapter 5.7, Host I/O caching, page 81)
• Guest Additions: added support for executing guest applications from the host system (replaces the automatic system preparation feature; see chapter 4.7, Guest control, page 69) • OVF: enhanced OVF support with custom namespace to preserve settings that are not part of the base OVF standard
• VMM: fixed Windows 2000 guest crash when configured with a large amount of RAM (bug #5800)
191 15 Change log
• GUI: added VM setting for passing the time in UTC instead of passing the local host time to the guest (bug #1310)
• GUI: fixed seamless mode on secondary monitors (bugs #1322 and #1669)• GUI: offer to download the user manual in the OSE version (bug #6442)• GUI: allow to set an empty host key to disallow any host key combination (bug #684)
• GUI: allow to restrict the possible actions when shutting down the VM from the GUI• Main: allow to start a VM even if a virtual DVD or floppy medium is not accessible• Settings: be more robust when saving the XML settings files• Mac OS X: rewrite of the CoreAudio driver and added support for audio input (bug #5869)
• 3D support: fixed blank screen after loading snapshot of VM with enabled Compiz• Added support for Virtual Distributed Ethernet (VDE) (Linux hosts only; see chapter 6.2, Introduction to networking modes, page 85)• Added support for virtual high precision event timer (HPET)
• OVF: fixed mapping between two IDE channels in OVF and the one IDE controller in VirtualBox• OVF: fix VMDK format string identifiers and sort XML elements from rasd: namespace alphabetically as prescribed by standard
• VBoxShell: interactive Python shell extended to be fully functional TUI for VirtualBox• Linux Additions: support Fedora 13 (bug #6370)• VBoxManage: fixed overly strict checks when creating a raw partition VMDK (bugs #688, #4438)
192 15 Change log
• VMM: fixed crash with the OpenSUSE 11.3 milestone kernel during early boot (software virtualization only) • VMM: fixed invalid state during teleportation • VMM: fixed OS/2 guest crash with nested paging enabled
• VMM: fixed massive display performance loss (AMD-V with nested paging only) • GUI: fixed off-by-one bug when passing absolute mouse coordinates to the guest (3.1.6 regression) • GUI: show the real version of the Guest Additions, not the interface version
• GUI: when adding a DVD or floppy slot in the VM mass storage settings dialog, don’t attach a random medium but just leave the slot empty • GUI: added --seamless and --fullscreen command line switches (bug #4220) • GUI: fixed a SEGFAULT under rare circumstances
• 2D Video acceleration: fixed display issues when working with non 32-bit modes (bugs #6094 & #6208) • LsiLogic: fixed detection of hard disks attached to port 0 when using the drivers from LSI • ATA: fixed sporadic crash with Linux guests when having a hard disk and DVD drive on the same channel (bug #6079) • Network: allow to start a VM even if not all network adapters are attached • Network: promiscuous mode support for e1000 and paravirtualized adapters (bug #6519) • NAT: fixed ICMP latency (non-Windows hosts only; bug #6427)
• SCSI: fixed guest crashes under certain circumstances when booting from SCSI devices • VBoxManage: fixed several bugs in cloning of images (one of them is bug #6408) • VBoxManage: fixed modifyvm –natnet default
• Solaris hosts: fixed a kernel panic when bridged networking might fail to initialize • Solaris hosts: fixed priority tagged VLAN packets in bridged networking • Shared Folders: fixed issue with copying read-only files (Linux guests only; bug #4890) • Shared Folders: renamed the guest kernel module from vboxvfs to vboxsf to make it load on demand by the Linux kernel. Fixes mounting from /etc/fstab in Ubuntu 10.04 • Shared Folders: fixed setuid file permissions (Solaris guests only) • Shared Folders: fixed deleting directories recursively (Solaris guests only; bug #6513) • Guest Additions: support seamless and dynamic resizing on certain older X11 guests (bug #5840) • Solaris Additions: fixed OpenGL library dependencies (bug #6435)
193 15 Change log
• Linux hosts: fixed timing issue on hosts with Linux kernels 2.6.31 or later with certain CPUs (asynchronous timer mode; bug #6250) • Linux hosts: properly handle host suspend/resume events on Linux kernels 2.6.30 or later (bug #5562) • Mac OS X hosts: fixed VBoxSVC crash while enumerating the host network interfaces under certain circumstances • Snapshots: fixed image corruption after snapshot merge under certain circumstances (bug #6023) • Snapshots: fixed crash with VBoxHeadless / OSE • VMM: fixed reference counting guru meditation (bug #4940) • VMM: improved guest SMP stability • VMM: fixed VT-x hardware debug issues (bugs #477 & #5792) • VMM: fixed PGMDynMapHCPage guru meditation (Mac OS X; VT-x only; bug #6095) • VMM: fixed pgmPoolTrackFlushGCPhysPTInt guru meditations (Mac OS X; VT-x only; bugs #6095 & #6125) • VMM: fixed host crash when running PAE guests in VT-X mode (Mac OS X only; bug #5771) • GUI: fix displaying of error message (bug #4345) • GUI: fix inability to enter seamless mode (bugs #6185, #6188) • 3D support: fixed assertion and flickering when guest application uses several windows with a single OpenGL context (bug #4598) • 3D support: fixed host crashes when using GL_EXT_compiled_vertex_array and array ele- ment calls (bug #6165)
194 15 Change log
• 3D support: fixed runtime linker errors with OpenGL guest libs (bug #5297)
• NAT: fixed memory corruption during ICMP traffic under certain circumstances• Network: allow to switch the host interface or the internal network while a VM is running (bug #5781)• VHD: fix for images with a block size different than 2MB
• Web service: update PHP bindings to fix problems with enums and collections
195 15 Change log
• VMM: added workaround for broken BIOSes that make VirtualBox think AMD-V is in use (for details see bug #5639) • VMM: fixed rare host reboot when restoring a saved state (bug #3945) • VMM: fixed incompatibility with 2.6.32 Linux kernels (software virtualization only; bug #6100) • VMM: turn on nested paging by default for new VMs (if available; VT-x and AMD-V only) • VMM: turn on VPID by default for new VMs (if available; VT-x only) • VMM: perform strict CPUID compatibility checks when teleporting; to get the old behavior set “VBoxInternal/CPUM/StrictCpuIdChecks” to 0 • VMM: fixed VM crash with certain 16 bits Windows applications (software virtualization only; bug #5399) • Snapshots: fixed a 3.1 regression that broke deletion of snapshots when a machine had immutable or writethrough storage attached (bug #5727) • Saved state: fixed VERR_SSM_LOADED_TOO_MUCH error when loading DisplayScreen- shot(bug #6162) • VBoxManage: add restorecurrent operation to snapshots command
196 15 Change log
• NAT: fixed high CPU load under certain circumstances (Windows hosts only; bug #5787)
• ATA: fix for guru meditation when installing Solaris 8 guests (bug #5972)• VHD: fixed an incompatibility with Virtual PC (bug #5990)• VHD: update the footer backup after setting a new UUID (bug #5004)• Host DVD: really fixed loading “passthrough” setting from configuration file (bug #5681)
• Solaris installer: fixed USB module removal and Solaris 10 “id” binary incompatibility• Guest Additions: fixed wrong guest time adjustment if the guest clock is ahead (3.1 regres- sion; non-Windows guests only)• Linux Additions: fixed shared folders for Linux 2.6.32 guests (bug #5891)
• Linux Additions: make the mouse driver work on Debian 5.0.3 guests again (3.1.2 regres- sion, bug #5832)• Windows Additions: fixed malfunctioning VBoxService that broke time-sync (bug #5872)• Windows Additions: fixed uninstallation issues on 64-bit guests
197 15 Change log
198 15 Change log
• Linux Guest Additions: fixed installation on RHEL 3.9 guests and on some 64bit guests • Linux Guest Additions: prevent SELinux warnings concerning text relocations in VBox- OGL.so (bug #5690) • X11 guests: fixed mouse support for some Xorg 1.4 guests (openSUSE 11.0) • X11 guests: fixed xorg.conf modification for some older Xorg releases (openSUSE 11.1) • Windows guests: fixed some VBoxService shutdown issues • Windows guests: fixed VBoxVideo spinlock issues on NT4 • Windows Guest Additions: fixed uninstallation issues of NT4 • Shared Folders: fixed resolving of symlink target (bug #5631) • 2D Video acceleration: delay loading of OpenGL dlls for Windows hosts to avoid GUI crashes on misconfigured systems • 2D Video acceleration: fixed issues with video picture not displayed on playback
• Teleportation (aka live migration); migrate a live VM session from one host to another (see chapter 7.2, Teleporting, page 98) • VM states can now be restored from arbitrary snapshots instead of only the last one, and new snapshots can be taken from other snapshots as well (“branched snapshots”; see chap- ter 1.9, Snapshots, page 23) • 2D video acceleration for Windows guests; use the host video hardware for overlay stretch- ing and color conversion (see chapter 4.4.2, Hardware 2D video acceleration for Windows guests, page 66) • More flexible storage attachments: CD/DVD drives can be attached to arbitrary storage controllers, and there can be more than one such drive (chapter 5, Virtual storage, page 72) • The network attachment type can be changed while a VM is running • Complete rewrite of experimental USB support for OpenSolaris hosts making use of the latest USB enhancements in Solaris Nevada 124 and higher • Significant performance improvements for PAE and AMD64 guests (VT-x and AMD-V only; normal (non-nested) paging) • Experimental support for EFI (Extensible Firmware Interface; see chapter 3.12, Alternative firmware (EFI), page 51) • Support for paravirtualized network adapters (virtio-net; see chapter 6.1, Virtual network- ing hardware, page 84)
199 15 Change log
• GUI: the log window grabbed all key events from other GUI windows (bug #5291)• GUI: allow to disable USB filters (bug #5426)• GUI: improved memory slider in the VM settings• 3D support: major performance improvement in VBO processing
• 3D support: fixed Final frame of Compiz animation not updated to the screen (bug #4653)• 3D support: fixed incorrect rendering of non ARGB textures under compiz• iSCSI: support iSCSI targets with more than 2TiB capacity
• VMDK: fixed incorrectly rejected big images split into 2G pieces (bug #5523, #2787)• VMDK: fixed compatibility issue with fixed or raw disk VMDK files (bug #2723)• VHD: fixed incompatibility with Hyper-V• Support for Parallels version 2 disk image (HDD) files; see chapter 5.2, Disk image files (VDI, VMDK, VHD, HDD), page 74• OVF: create manifest files on export and verify the content of an optional manifest file on import• OVF: fixed memory setting during import (bug #4188)
• Mouse device: now five buttons are passed to the guest (bug #3773)• VBoxHeadless: fixed loss of saved state when VM fails to start• VBoxSDL: fixed crash during shutdown (Windows hosts only)• X11 based hosts: allow the user to specify their own scan code layout (bug #2302)
• Mac OS X hosts: don’t auto show the menu and dock in fullscreen (bug #4866)• Mac OS X hosts (64 bit): don’t interpret mouse wheel events as left click (bug #5049)• Mac OS X hosts: fixed a VM abort during shutdown under certain conditions
• Solaris hosts: combined the kernel interface package into the VirtualBox main package• Solaris hosts: support for OpenSolaris Boomer architecture (with OSS audio backend)• Shared Folders: VBOXSVR is visible in Network folder (Windows guests, bug #4842)
200 15 Change log
201 15 Change log
• VMM: guru meditation during SCO OpenServer installation and reboot (VT-x only; bug #5164) • VMM: fixed accessed bit handling in certain cases (bug #5248) • VMM: fixed VPID flushing (VT-x only)
• VMM: fixed broken nested paging for 64 bits guests on 32 bits hosts (AMD-V only; bug #5285) • VMM: fixed loading of old saved states/snapshots (bug #3984) • Mac OS X hosts: fixed memory leaks (bug #5084)
• Mac OS X hosts (Snow Leopard): fixed redraw problem in a dual screen setup (bug #4942) • Windows hosts: installer updates for Windows 7 • Solaris hosts: out of memory handled incorrectly (bug #5241)
• Solaris hosts: the previous fix for #5077 broke the DVD host support on Solaris 10 (VBox 3.0.8 regression) • Linux hosts: fixed module compilation against Linux 2.6.32rc4 and later • Guest Additions: fixed possible guest OS kernel memory exhaustion
• Linux installer: register the module sources at DKMS even if the package provides proper modules for the current running kernel • 3D support: removed invalid OpenGL assertion (bug #5158)
• Network: fixed the Am79C973 PCNet emulation for QNX (and probably other) guests (bug #3206) • VMDK: fix handling of split image variants
202 15 Change log
• VHD: do not delay updating the footer when expanding the image to prevent image incon- sistency
• Shared clipboard/X11 hosts: fixed a crash when clipboard initialisation failed (bug #4987)
• VMM: fixed 64 bits guest on 32 bits host regression in 3.0.6 (VT-x only; bug #4947) • VMM: fixed a recompiler triple fault guru meditation (VT-x & AMD-V only; bug #5058) • VMM: fixed hang after guest state restore (AMD-V, 32 bits Windows guest and IO-APIC enabled only; bug #5059) • VMM: fixed paging issue with OS/2 guests • VMM: fixed guru meditation in rare cases (2.0 regression; software virtualization only) • VMM: fixed release assertion during state restore when using the Sound Blaster 16 emula- tion (bug #5042) • Security: fixed vulnerability that allowed to execute commands with root privileges • Linux hosts: fixed runtime assertion in semaphore implementation which was triggered under certain conditions (bug #616)
• Linux hosts: change the default USB access mode on certain distributions (bugs #3394 and #4291) • Linux hosts: on hardened Gentoo, the VBoxSVC daemon crashed by opening the VM net- work settings (bug #3732) • Linux hosts, Solaris hosts: pass the XAUTHORITY variable along the DISPLAY variable when starting a VM from VBoxManage or from the VM selector (bug #5063) • Linux hosts: use sysfs to enumerate host drives if hal is not available • Solaris hosts: fixed a bug which would hang the host sporadically as interrupts were not re-enabled every time
• Solaris hosts: fixed a kernel panic with bridged and host-only networking (bug #4775) • Solaris hosts: fixed incorrectly persistent CD/DVD-ROMs when changing them (bug #5077) • X11-based hosts: support additional function keys on Sun keyboards (bug #4907)
• Mac OS X hosts (Snow Leopard): fixed problem starting headless VMs without a graphical session (bug #5002) • Mac OS X hosts: fixed problem listing host-only adapter names with trailing garbage (at- tached VMs won’t start)
203 15 Change log
• Windows Additions: now work with Vista 64-bit Home editions (bug #3865) • Windows Additions: fixed screen corruption with ZoomText Magnifier • Windows Additions: fixed NPGetUniversalName failure (bug #4853) • Windows Additions: fixed Windows NT regression (bug #4946) • Windows Additions: fixed VBoxService not running if no Shared Folders are installed • Linux Additions: implemented ftrunctate (bug #4771) • VRDP: start VM even if configured VRDP port is in use • Networking: the PCnet network device stopped receiving under rare conditions (bug #4870) • VBoxManage: implemented controlvm vrdpport command • iSCSI: fixed issue with NetApp targets (bug #5072) • SCSI: add support for virtual disks larger than 2TB • USB: fixed potential crash when unplugging USB2 devices (bug #5089) • NAT: IPSEC did not properly work with Linux guests (bug #4801)
• VMM: fixed IO-APIC overhead for 32 bits Windows NT, 2000, XP and 2003 guests (AMD-V only; bug #4392) • VMM: fixed a Guru meditation under certain circumstances when enabling a disabled de- vice (bug #4510) • VMM: fixed a Guru meditation when booting certain Arch Linux guests (software virtual- ization only; bug #2149) • VMM: fixed hangs with 64 bits Solaris & OpenSolaris guests (bug #2258) • VMM: fixed decreasing rdtsc values (AMD-V & VT-x only; bug #2869) • VMM: small Solaris/OpenSolaris performance improvements (VT-x only) • VMM: cpuid change to correct reported virtual CPU ID in Linux • VMM: NetBSD 5.0.1 CD hangs during boot (VT-x only; bug #3947) • Solaris hosts: worked around an issue that caused the host to hang (bug #4486) • Solaris hosts: fixed a rare host system deadlock when using bridged networking • Solaris hosts: fixed a potential host system deadlock when CPUs were onlined or offlined • Solaris hosts installer: added missing dependency for UTF-8 package (bug #4899) • Linux hosts: don’t crash on Linux PAE kernels < 2.6.11 (in particular RHEL/CentOS 4); disable VT-x on Linux kernels < 2.6.13 (bug #1842) • Linux/Solaris hosts: correctly detect keyboards with fewer keys than usual (bug #4799)
204 15 Change log
• Python WS: fixed issue with certain enumerations constants having wrong values in Python webservices bindings• Python API: several threading and platform issues fixed• Python shell: added exportVM command
• Serial: fixed host mode (Solaris, Linux and Mac OS X hosts; bug #4672)• VRDP: Remote USB Protocol version 3• SATA: fixed hangs and BSODs introduced with 3.0.4 (bugs #4695, #4739, #4710)• SATA: fixed a bug which prevented Windows 7 from detecting more than one hard disk
• Mouse: fixed weird mouse behaviour with SMP (Solaris) guests (bug #4538)• HostOnly Network: fixed failure in CreateHostOnlyNetworkInterface() on Linux (no GUID)• HostOnly Network: fixed wrong DHCP server startup while hostonly interface bringup on Linux
• HostOnly Network: fixed incorrect factory and default MAC address on Solaris• HostOnly Network: fixed the problem with listing host-only interfaces on Mac OS X when all physical interfaces are down (bugs #4698, #4790)
205 15 Change log
• DHCP: fixed a bug in the DHCP server where it allocated one IP address less than the configured range • E1000: fixed receiving of multicast packets • E1000: fixed up/down link notification after resuming a VM • NAT: fixed ethernet address corruptions (bug #4839) • NAT: fixed hangs, dropped packets and retransmission problems (bug #4343) • Bridged networking: fixed packet queue issue which might cause DRIVER_POWER_STATE_FAILURE BSOD for Windows hosts (bug #4821) • Windows Additions: fixed a bug in VBoxGINA which prevented selecting the right domain when logging in the first time • Windows host installer: should now also work on unicode systems (like Korean, bug #3707) • Windows host installer: check for sufficient disk space • Shared clipboard: do not send zero-terminated text to X11 guests and hosts (bug #4712) • Shared clipboard: use a less CPU intensive way of checking for new data on X11 guests and hosts (bug #4092) • Guest Additions: do not hide the host mouse cursor when restoring a saved state (bug #4700) • Windows guests: fixed issues with the display of the mouse cursor image (bugs #2603, #2660 and #4817) • SUSE 11 guests: fixed Guest Additions installation (bug #4506) • Guest Additions: support Fedora 12 Alpha guests (bugs #4731, #4733 and #4734)
• VMM: 64 bits guest stability fixes (AMD-V only; bugs #3923 & #3666) • VMM: SMP stability fixes (AMD-V only) • VMM: SMP performance improvement (esp. for Solaris guests) • VMM: eliminated several bugs which could lead to a host reboot • VMM: fixed OS/2 ACP2 boot floppy hang (VT-x only) • VMM: small performance improvement for OpenSolaris guests (AMD-V only) • VMM: fixed CentOS/Xen reboot (software virtualization only; bug #4509) • SATA: fixed hangs / BSOD during Windows XP installation (bug #4342) • SATA: mark the ports as non hotpluggable (bug #3920) • 3D support: fix deadlocks and context/window tracking for multithreaded applications (bug #3922)
206 15 Change log
• GUI: don’t crash when adding plus configuring host-only network interfaces• Shared Folders: fixed selection of a drive root directory as a shared folder host path in VirtualBox (Windows host only)• USB: fixed a bug that may have rendered USB device filter settings inactive (3.0.2 regres- sion, bug #4668)• Guest Additions: report the Guest Additions version to the guest properties (bug #3415)• Mac OS X hosts: fix creation of VMDK files giving raw partition access (bug #1461)
• Linux and Solaris hosts: Work around color handling problems in Qt (bug #4353)• Solaris hosts: fixed memory leaks in host-only networking• Solaris Installer: fixed incorrect netmask for Host-only interface (bug #4590)• Solaris Installer: added package dependency for Python and Python-devel (bug #4570)
• X11 guests: prevent windows from being skipped in seamless mode KDE guests (bugs #1681 and #3574)• X11 guests: fixed screen corruption in X11 guests when large amounts of video RAM were allocated (bug #4430)
• X11 guests: some fixes when switching between host and guest-drawn mouse pointers• X11 guests: fixed an issue which caused seamless mode to stop working as it should (the main issue listed in bug #2238)
207 15 Change log
• VMM: fixed network regressions (guest hangs during network IO) (bug #4343) • VMM: guest SMP performance improvements • VMM: fixed hangs and poor performance with Kaspersky Internet Security (VT-x/AMD-V only; bug #1778) • VMM: fixed crashes when executing certain Linux guests (software virtualization only; bugs #2696 & #3868) • ACPI: fixed Windows 2000 kernel hangs with IO-APIC enabled (bug #4348) • APIC: fixed high idle load for certain Linux guests (3.0 regression) • BIOS: properly handle Ctrl-Alt-Del in real mode • iSCSI: fixed configuration parsing (bug #4236) • OVF: fix potential confusion when exporting networks • OVF: compatibility fix (bug #4452) • OVF: accept ovf:/disk/ specifiers with a single slash in addition to ovf://disk/ (bug #4452) • NAT: fixed crashes under certain circumstances (bug #4330) • 3D support: fixed dynamic linking on Solaris/OpenSolaris guests (bug #4399) • 3D support: fixed incorrect context/window tracking for multithreaded apps • Shared Folders: fixed loading from saved state (bug #1595) • Shared Folders: host file permissions set to 0400 with Windows guest (bug #4381) • X11 host and guest clipboard: fixed a number of issues, including bug #4380 and #4344 • X11 Additions: fixed some issues with seamless windows in X11 guests (bug #3727) • Windows Additions: added VBoxServiceNT for NT4 guests (for time synchronization and guest properties) • Windows Additions: fixed version lookup • Linux Installer: support Pardus Linux • Linux hosts: workaround for buggy graphics drivers showing a black VM window on recent distributions (bug #4335) • Linux hosts: fixed typo in kernel module startup script (bug #4388) • Solaris hosts: several installer fixes • Solaris host: fixed a preemption issue causing VMs to never start on Solaris 10 (bug #4328) • Solaris guest: fixed mouse integration for OpenSolaris 2009.06 (bug #4365) • Windows hosts: fixed high CPU usage after resuming the host (bug #2978) • Fixed a settings file conversion bug which sometimes caused hardware acceleration to be enabled for virtual machines that had no explicit configuration in the XML
208 15 Change log
• Guest SMP with up to 32 virtual CPUs (VT-x and AMD-V only; see chapter 3.4.2, “Processor” tab, page 44) • Windows guests: ability to use Direct3D 8/9 applications / games (experimental; see chap- ter 4.4.1, Hardware 3D acceleration (OpenGL and Direct3D 8/9), page 65) • Support for OpenGL 2.0 for Windows, Linux and Solaris guests
• Solaris hosts: allow suspend/resume on the host when a VM is running (bug #3826) • Solaris hosts: loosen the restriction for contiguous physical memory under certain condi- tions • Mac OS X hosts: fixed guest PAE • Linux hosts: kernel module compile fixes for 2.6.31 (bug #4264) • VMM: fixed occasional guru meditation when loading a saved state (VT-x only) • VMM: eliminated IO-APIC overhead with 32 bits guests (VT-x only, some Intel CPUs don’t support this feature (most do); bug #638) • VMM: fixed 64 bits CentOS guest hangs during early boot (AMD-V only; bug #3927) • VMM: performance improvements for certain PAE guests (e.g. Linux 2.6.29+ kernels) • VMM: some Windows guests detected a completely wrong CPU frequency (bug #2227) • VMM: fixed hanging and unkillable VM processes (bug #4040) • VMM: fixed 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 • GUI: allow to create/remove more than one host-only network adapters (non Windows hosts) • GUI: display estimated time for long running operations (e.g. OVF import/export) • GUI: fixed rare hangs when open the OVF import/export wizards (bug #4157) • 3D support: fixed VM crashes for client applications using incorrect OpenGL states • 3D support: fixed memory corruption when querying for supported texture compression formats • 3D support: fixed incorrect rendering of glDrawRangeElements • 3D support: fixed memory leak when using VBOs • 3D support: fixed glew library detection • 3D support: fixed random textures corruption
209 15 Change log
210 15 Change log
• Web service: fixed 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 inheritance correctly, fixed • Web service: added support for IDisplay and IGuest interfaces, which were previously unavailable • Registration dialog uses Sun Online accounts now
211 15 Change log
• Host and guest clipboard: fixed a number of issues affecting hosts and guests running the X window system • Guest Additions: make sure the virtual mouse autodetection works on first reboot 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 • Linux Additions: fixed installation path for OpenGL libraries in some 64-bit guests (bug #3693) • Solaris Additions: fixed installation to work when X.Org is not installed on the guest • Solaris Additions: fixed a bug that could panic the guest when unmounting a busy shared folder • Windows Additions: fixed mouse pointer integration of some Windows guests (2.2.0 re- gression, bug #3734) • Windows Additions: fixed installation on Windows Server 2008 Core (bug #2628) • Main: do not try to use older versions of D-Bus (Linux hosts only, bug #3732) • VMM: fixed out-of-memory conditions on Windows hosts (bug #3657) • VMM: fixed occasional hangs when attaching USB devices during VM startup (2.2.0 regres- sion; bugs #3787)
212 15 Change log
• VMM: fixed guru meditation related to memory management (software virtualization only) • Virtual disks: fix possible data corruption when writing to diff images, incorrect detection of redundant writes • GUI: reworked network settings dialog • GUI: properly show the detailed settings dialog of NAT networks (bug #3702) • GUI: HostKey could not be changed (2.2.0 regression, bug #3689) • GUI: fixed memory textfield size (Windows hosts only; bug #3679) • GUI: fixed crash when selecting a shared folder path (Windows hosts only; bugs #3694, #3751, #3756) • VBoxManage modifyhd --compact: implemented again for VDI files, 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: fixed release assertion during poll() (bug #3667) • Networking: fixed a deadlock caused by the PCnet network device emulation (2.2.0 regres- sion, bug #3676) • Clipboard: fixed random crashes (X11 hosts only, bug #3723) • Shared Folders: fixed incorrect permissions for Solaris guests • Shared Folders: fixed wrong file sizes with Solaris guests • CBindings: fixed possible memory leak while releasing the IVirtualBox and ISession Objects • Solaris hosts: fixed host-only network interface incompatibility with nwam/dhcpagent (bug #3754) • Windows installer: fixed several install and uninstall issues (bugs #3659, #3686, #1730, #3711, #3373, #3382, #3701, #3685, #3710) • Mac OS X hosts: preliminary support for Snow Leopard
• OVF (Open Virtualization Format) appliance import and export (see chapter 1.12, Import- ing and exporting virtual machines, page 26) • Host-only networking mode (see chapter 6.6, Host-only networking, page 89))
213 15 Change log
• VMM: FreeBSD guest related fix for V86 flags (bug #2342)T-x/AMD-V only)
• VMM: significant speedup of certain GRUB boot loaders (e.g. Solaris) (VT-x VMM: emulate RDPMC; fixes Windows guests crashes when using the Kaspersky virus scan- ner (bug #1778)
• Hard disk: support more VMDK file variants (including fixed-size ESX server images) • Hard disks: refuse to start the VM if a disk image is not writable • USB: further reduced host CPU utilization for OHCI and EHCI; the “VBoxInternal/Devices/usb- oh Shared Folders: respect umask settings on Linux, OSX and Solaris hosts when creating files • X11 guests: prevented setting the locale in vboxmouse, as this caused problems with Turk- ish locales (bug #3563)
214 15 Change log
• X11 guests: show the guest mouse pointer at the right position if the virtual desktop is larger than the guest resolution (bug #2306)• Linux Additions: fixed typo when detecting Xorg 1.6 (bug #3555)•• Windows installers: combined installer executable which contains both (32- and 64-bit) architectures• VBoxManage: less cryptic command-line error messages• VBoxManage list vms commands now default to compact format• VBoxManage controlvm dvdattach did not work if the image was attached before• VBoxManage: allow creation of all supported disk image variants• VBoxManage showvminfo: don’t spam the release log if the Guest Additions don’t support statistics information (bug #3457)• VBoxManage: big command line processing cleanup, the legacy single-dash options 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 file 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• GUI: deactivate 64-bit guest support when the host CPU does not support VT-x/AMD-V• GUI: removed floppy icon from the status bar• GUI: show build revision in about dialog• GUI: fixed sticky status bar text• GUI: improved error dialogs• GUI: fail with an appropriate error message when trying to boot a read-only disk image (bug #1745)• GUI/Mac OS X: fixed disabled close button• GUI/Windows: re-enabled support for copy and paste (Windows hosts 2.0 regression; bug #2065)• 3D support: added OpenGL select/feedback support (bug #2920)
215 15 Change log
• Main API: close machine settings XML file when unregistering machine (bug #3548)
• Windows hosts: fixed host crashes/hangs on certain 32 bits Windows systems when run- ning Linux guests (bugs #1606, #2269, #2763) • Windows hosts: fixed network component BSOD issue (bugs #3168, #2916)
• Linux hosts: fixed warnings in installer when SELinux was disabled (bug #3098) • Linux hosts: VirtualBox sometimes failed to start if it had been started using sudo previ- ously (bug #3270) • Solaris hosts: fixed high CPU load while running many guests in parallel
• REM: fixed inability to use gdb to debug programs in Linux guests with software virtual- ization (bug #3245))
216 15 Change log•• 3D support: added missing GL_MAX_TEXTURE_COORDS_ARB (bug #3246)
• Windows Additions: fixed ERROR (e0000101) error during installation (bug #1923)• Windows Additions: fixed Windows Explorer hang when browsing shared folders with 64 bit guests (bug #2225)• Windows Additions: fixed guest screen distortions during a video mode change
• Windows Additions: fixed the Network drive not connected message for mapped shared folders drives after the guest startup (bug #3157 ac- tual guest resolution (bug #3096)
217 15 Change log
• VMM: fixed guru meditation when booting Novell Netware 4.11 (VT-x only; bug #2898) • VMM: fixed VERR_ADDRESS_TOO_BIG error on some Mac OS X systems when starting a VM • VMM: clear MSR_K6_EFER_SVME after probing for AMD-V (bug #3058)
• VMM: fixed guru meditation during Windows 7 boot with more than 2 GB guest RAM (VT-x, nested paging only) • VMM: fixed hang during OS/2 MCP2 boot (AMD-V and VT-x only) • VMM: fixed loop during OpenBSD 4.0 boot (VT-x only)
• VMM: fixed random crashes related to FPU/XMM with 64 bits guests on 32 bits hosts • VMM: fixed occasional XMM state corruption with 64 bits guests • GUI: raised the RAM limit for new VMs to 75% of the host memory • GUI: added Windows 7 as operating system type
• VGA: better handling for VRAM offset changes (fixes GRUB2 and Dos DOOM display issues) • VGA: custom VESA modes with invalid widths are now rounded up to correct ones (bug #2895) • IDE: fixed ATAPI passthrough support (Linux hosts only; bug #2795)
• Networking: fixed kernel panics due to NULL pointer dereference in Linux kernels < 2.6.20 (Linux hosts only; bug #2827)
218 15 Change log
• Networking: fixed intermittent BSODs when using the new host interface (Windows hosts only; bugs #2832, #2937, #2929)
• Networking: fixed several issues with displaying hostif NICs in the GUI (Windows hosts only; bugs 2814, #2842)• Networking: fixed the issue with displaying hostif NICs without assigned IP addresses (Linux hosts only; bug #2780)
• Networking: fixed the issue with sent packets coming back to internal network when using hostif (Linux hosts only; bug #3056).• NAT: fixed port forwarding (Windows hosts only; bug #2808)• NAT: fixed booting from the builtin TFTP server (bug #1959)
• SATA: fixed timeouts in the guest when using raw VMDK files (Linux host only, bug #2796)• SATA: huge speed up during certain I/O operations like formatting a drive• SATA/IDE: fixed possible crash/errors during VM shutdown• VRDP: fixed loading of libpam.so.1 from the host (Solaris hosts only)
• VHD: fixed error when attaching certain container files (bug #2768)• Solaris hosts: added support for serial ports (bug #1849)• Solaris hosts: fix for Japanese keyboards (bug #2847)• Solaris hosts: 32-bit and 64-bit versions now available as a single, unified package
• Mac OS X hosts: save the state of running or paused VMs when the host machine’s battery reaches critical level• Mac OS X hosts: improved window resizing of the VM window
219 15 Change log
• Mac OS X hosts: added GUI option to disable the dock icon realtime preview in the GUI to decrease the host CPU load when the guest is doing 3D
• Windows Additions: fixed Windows 2000 guest freeze when accessing files on shared fold- ers (bug #2764) • Windows Additions: fixed CTRL-ALT-DEL handling when using VBoxGINA • Windows Additions Installer: added /extract switch to only extract (not install) the files to a directory (can be specified with /D=path) • Linux installer and Additions: added support for the Linux From Scratch distribution (bug #1587) and recent Gentoo versions (bug #2938) • Additions: added experimental support for X.Org Server 1.6 RC on Linux guests
• Linux Additions: fixed bug which prevented to properly set fmode on mapped shared fold- ers (bug #1776) • Linux Additions: fixed appending of files on shared folders (bug #1612) • Linux Additions: ignore noauto option when mounting a shared folder (bug #2498)
• Linux Additions: fixed 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)
• Full VMDK/VHD support including snapshots (see chapter 5.2, Disk image files (VDI, VMDK, VHD, HDD), page 74) • New NAT engine with significantly better performance, reliability and ICMP echo (ping) support (bugs #1046, #2438, #2223, #1247)
220 15 Change log
• New Host Interface Networking implementations for Windows and Linux hosts with easier setup (replaces TUN/TAP on Linux and manual bridging on Windows)
221 15 Change log
• VBoxManage: fixed bug which prevented setting up the serial port for direct device access
• Shared Folders: performance and stability fixes for Windows guests (Microsoft Office Ap- plications)
• VMM: fixed guest hangs when restoring VT-x or AMD-V saved states/snapshots • VMM: fixed memory allocation issues which can cause VM start failures with VERR_PGM_MAPPING_CONFLICT error • VMM: fixed host crashes/hangs on certain 32 bits Windows systems when running Linux guests (bugs #1606, #2269, #2763) • XPCOM/Main: fixed synchronization bug caused by SYSV semaphore key collisions
• ATA: fixed deadlock when pausing VM due to problems with the virtual disk (e.g. disk full, iSCSI target unavailable) • iSCSI: fixed possible crash when pausing the VM • iSCSI: fix PDU validity checking and detect final PDU reliably
• VBoxHeadless: really don’t start X11 services (clipboard service, 3D acceleration; Solaris & Darwin hosts only; bug #3199) • Networking: fixed issue where a VM could lose connectivity after a reboot • Linux hosts: fixed occasional kernel oopses (bug #2556)
• Solaris hosts: fixed high CPU load while running many guests in parallel • Solaris hosts: fixed inability to start more than 128 VMs • Solaris/Web services: fixed SMF script to set home directory correctly • Linux Additions: fixed occasional file corruption when writing files in O_APPEND mode to a shared folder (bug #2844)
222 15 Change log
• VMM: fixed Guru meditation when running 64 bits Windows guests (bug #2220) • VMM: fixed Solaris 10U6 boot hangs (VT-x and AMD-V) bug #2565) • VMM: fixed Solaris 10U6 reboot hangs (AMD-V only; bug #2565)
• GUI: the host key was sometimes not properly displayed (Windows hosts only, bug #1996) • GUI: the keyboard focus was lost after minimizing and restoring the VM window via the Windows taskbar (bugs #784) • VBoxManage: properly show SATA disks when showing the VM information (bug #2624)
• SATA: fixed access if the buffer size is not sector-aligned (bug #2024) • SATA: improved performance • SATA: fixed snapshot function with ports>1 (bug #2510) • E1000: fixed crash under rare circumstances
• USB: fixed support for iPhone and Nokia devices (Linux host: bugs #470 & #491) • Windows host installer: added proper handling of open VirtualBox applications when up- dating the installation • Windows host installer: fixed default installation directory on 64-bit on new installations (bug #2501) • Linux/Solaris/Darwin hosts: verify permissions in /tmp/vbox-$USER-ipc • Linux hosts: fixed assertion on high network load (AMD64 hosts, fix 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: fixed incompatibility between IPSEC and host interface networking • Solaris hosts: fixed a rare race condition while powering off VMs with host interface net- working
• Solaris hosts: fixed VBoxSDL on Solaris 10 by shipping the required SDL library (bug #2475) • Windows Additions: fixed logged in users reporting via guest properties when using native RDP connections
• Windows Additions: fixed Vista crashes when accessing shared folders under certain cir- cumstances (bug #2461) • Windows Additions: fixed shared folders access with MS-Office (bug #2591) • Linux Additions: fixed compilation of vboxvfs.ko for 64-bit guests (bug #2550)
223 15 Change log
224 15 Change log
• VMM: fixed inability to run more than one VM in parallel (AMD-V on CPUs with erratum 170 only; bug #2167) • VMM: VT-x stability fixes (bug #2179 and others) • VMM: fixed Linux 2.6.26+ kernel crashes (used by Ubuntu 8.10 Alpha, Fedora 10 Alpha; bug #1875) • VMM: fixed 64 bits Linux 2.6.26 kernel crashes (Debian)) • GUI: fixed standard menu entries for NLS versions (Mac OS X hosts only) • GUI: disable the VT-x/AMD-V setting when it’s not supported by the CPU (or on Mac OS X hosts)
225 15 Change log
226 15 Change log
• Created separate SDK component featuring a new Python programming interface on Linux and Solaris hosts
With VirtualBox 3.2, changelog information for versions before 2.0 was removed in order tosave space. To access this information, please consult the User Manual of VirtualBox version 3.1or earlier.
22716 Third-party materials and licensesVirtualBox incorporates materials from several Open Source software projects. Therefore the useof these materials by VirtualBox is governed by different Open Source licenses. This documentreproduces these licenses and provides a list of the materials used and their respective licensingconditions. Section 1 contains a list of the materials used. Section 2 reproduces the applicableOpen Source licenses. For each material, a reference to its license is provided. The source code for the materials listed below as well as the rest of the VirtualBox code whichis released as open source are available at, both as tarballs forparticular releases and as a live SVN repository.
16.1 Materials • VirtualBox contains portions of QEMU which is governed by the licenses in chapter 16.2.5, X Consortium License (X11), page 245 and chapter 16.2.2, GNU Lesser General Public License (LGPL), page 234 and (C) 2003-2005 Fabrice Bellard; Copyright (C) 2004-2005 Vassili Karpov (malc); Copyright (c) 2004 Antony T Curtis; Copyright (C) 2003 Jocelyn Mayer • VirtualBox contains code which is governed by the license in chapter 16.2.5, X Consortium License (X11), page 245 and Copyright 2004 by the Massachusetts Institute of Technology. • VirtualBox contains code of the BOCHS VGA BIOS which is governed by the license in chapter 16.2.2, GNU Lesser General Public License (LGPL), page 234 and Copyright (C) 2001, 2002 the LGPL VGABios developers Team. • VirtualBox contains code of the BOCHS ROM BIOS which is governed by the license in chapter 16.2.2, GNU Lesser General Public License (LGPL), page 234 and Copyright (C) 2002 MandrakeSoft S.A.; Copyright (C) 2004 Fabrice Bellard; Copyright (C) 2005 Struan Bartlett. • VirtualBox contains the zlib library which is governed by the license in chapter 16.2.6, zlib license, page 245 and Copyright (C) 1995-2003 Jean-loup Gailly and Mark Adler. • VirtualBox may contain OpenSSL which is governed by the license in chapter 16.2.7, OpenSSL license, page 245 and Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). • VirtualBox may contain NSPR and XPCOM which is governed by the license in chapter 16.2.3, Mozilla Public License (MPL), page 239 and Copyright (C) The Authors. • VirtualBox contains Slirp which is governed by the license in chapter 16.2.8, Slirp license, page 246 and was written by Danny Gasparovski. Copyright (C) 1995, 1996 All Rights Reserved.
228 16 Third-party materials and licenses
• VirtualBox contains liblzf which is governed by the license in chapter 16.2.9, liblzf license, page 247 and Copyright (C) 2000-2005 Marc Alexander Lehmann <schmorp@schmorp.de>• VirtualBox may ship with a modified copy of rdesktop which is governed by the license in chapter 16.2.1, GNU General Public License (GPL), page 230 and Copyright (C) Matthew Chapman and others.• VirtualBox may ship with a copy of kchmviewer which is governed by the license in chapter 16.2.1, GNU General Public License (GPL), page 230 and Copyright (C) George Yunaev and others.• VirtualBox may contain Etherboot which is governed by the license in chapter 16.2.1, GNU General Public License (GPL), page 230 with the exception that aggregating Etherboot with another work does not require the other work to be released under the same license (see). Etherboot is Copyright (C) Etherboot team.• VirtualBox contains code from Wine which is governed by the license in chapter 16.2.2, GNU Lesser General Public License (LGPL), page 234 the license in chapter 16.2.11, lwIP license, page 247 and Copyright (C) 2001, 2002 Swedish Institute of Computer Science.• VirtualBox contains libxml which is governed by the license in chapter 16.2.12, libxml license, page 248 and Copyright (C) 1998-2003 Daniel Veillard.• VirtualBox contains libxslt which is governed by the license in chapter 16.2.13, libxslt li- censes, page 248 and Copyright (C) 2001-2002 Daniel Veillard and Copyright (C) 2001-2002 Thomas Broyer, Charlie Bozeman and Daniel Veillard.• VirtualBox contains code from the gSOAP XML web services tools, which are licensed under the license in chapter 16.2.14, gSOAP Public License Version 1.3a, page 249 and Copyright (C) 2000-2007, Robert van Engelen, Genivia Inc., and others.• VirtualBox ships with the application tunctl (shipped as VBoxTunctl) from the User-mode Linux suite which is governed by the license in chapter 16.2.1, GNU General Public License (GPL), page 230 and Copyright (C) 2002 Jeff Dike.• VirtualBox contains code from Chromium, an OpenGL implementation, which is goverened by the licenses in chapter 16.2.15, Chromium licenses, page 254 and Copyright (C) Stanford University, The Regents of the University of California, Red Hat, and others.• VirtualBox contains libcurl which is governed by the license in chapter 16.2.16, curl license, page 256 and Copyright (C) 1996-2009, Daniel Stenberg.
229 16 Third-party materials and licenses
• VirtualBox contains dnsproxy which is governed by the license in chapter 16.2.4, MIT Li- cense, page 245 and Copyright (c) 2003, 2004, 2005 Armin Wolfermann. • VirtualBox may contain iniparser which is governed by the license in chapter 16.2.4, MIT License, page 245 and Copyright (c) 2000-2008 by Nicolas Devillard.
• VirtualBox contains some code from libgd which is governed by the license in chapter 16.2.17, libgd license, page 256 and Copyright 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007 Pierre-Alain Joye (pierre@libgd.org). • VirtualBox contains code from the EFI Development Kit II which is governed by the license in chapter 16.2.18, BSD license from Intel, page 257 and Copyright (c) 2004-2008, Intel Corporation. • VirtualBox contains libjpeg which is governed by the license in chapter 16.2.19, libjpeg License, page 257 and Copyright (C) 1991-2010, Thomas G. Lane, Guido Vollbeding. • VirtualBox may contain x86 SIMD extension for IJG JPEG library which is governed by the license in chapter 16.2.20, x86 SIMD extension for IJG JPEG library license, page 258 and Copyright 2009 Pierre Ossman <ossman@cendio.se> for Cendio AB; Copyright 2010 D. R. Commander; Copyright (C) 1999-2006, MIYASAKA Masaru.
16.2 Licenses16.2.1 GNU General Public License (Gchanging it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and changeit. By contrast, the GNU General Public License is intended to guarantee your freedom to shareand change free software–to make sure the software is free for all its users. This General PublicLicense applies to most of the Free Software Foundation’s software and to any other programwhose authors commit to using it. (Some other Free Software Foundation software is covered bythe GNU Library General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General PublicLicenses are designed to make sure that you have the freedom to distribute copies of free software(and charge for this service if you wish), that you receive source code or can get it if you wantit, that you can change the software or use pieces of it in new free programs; and that you knowyou can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you theserights or to ask you to surrender the rights. These restrictions translate to certain responsibilitiesfor you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you mustgive the recipients all the rights that you have. You must make sure that they, too, receive or canget the source code. And you must show them these terms so they know their rights.
230 16 Third-party materials and licenses
We protect your rights with two steps: (1) copyright the software, and (2) offer you this licensewhich gives you legal permission to copy, distribute and/or modify the software. Also, for each author’s protection and ours, we want to make certain that everyone under-stands that there is no warranty for this free software. If the software is modified by someoneelse and passed on, we want its recipients to know that what they have is not the original, sothat any problems introduced by others will not reflect on the original authors’ reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid thedanger that redistributors of a free program will individually obtain patent licenses, in effectmaking the program proprietary. To prevent this, we have made it clear that any patent must belicensed for everyone’s free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTIONAND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by thecopyright holder saying it may be distributed under the terms of this General Public License.The “Program”, below, refers to any such program or work, and a “work based on the Program”means either the Program or any derivative work under copyright law: that is to say, a workcontaining the Program or a portion of it, either verbatim or with modifications and/or trans-latedthe Program is covered only if its contents constitute a work based on the Program (independentof having been made by running the Program). Whether that is true depends on what theProgram does. 1. You may copy and distribute verbatim copies of the Program’s source code as you receiveit, in any medium, provided that you conspicuously and appropriately publish on each copy anappropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer tothis License and to the absence of any warranty; and give any other recipients of the Program acopy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your optionoffer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming awork based on the Program, and copy and distribute such modifications or work under the termsof Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed thefiles and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part containsor is derived from the Program or any part thereof, to be licensed as a whole at no charge to allthird parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must causeit, when started running for such interactive use in the most ordinary way, to print or display anannouncement including an appropriate copyright notice and a notice that there is no warranty(or else, saying that you provide a warranty) and that users may redistribute the program underthese conditions, and telling the user how to view a copy of this License. (Exception: if theProgram itself is interactive but does not normally print such an announcement, your workbased on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that workare not derived from the Program, Program, the distribution of the whole must be on the terms of this
231 16 Third-party materials and licenses
License, Program. In addition, mere aggregation of another work not based on the Program with the Program(or with a work based on the Program) on a volume of a storage or distribution medium doesnot bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in objectcode or executable form under the terms of Sections 1 and 2 above provided that you also doone of the following: a) Accompany it with the complete corresponding machine-readable source code, which mustbe distributed under the terms of Sections 1 and 2 above on a medium customarily used forsoftware interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party,for a charge no more than your cost of physically performing source distribution, a completemachine-readable copy of the corresponding source code, to be distributed under the terms ofSections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute correspond-ing source code. (This alternative is allowed only for noncommercial distribution and only ifyou received the program in object code or executable form with such an offer, in accord withSubsection b above.) The source code for a work means the preferred form of the work for making modifications toit. For an executable work, complete source code means all the source code for all modules itcontains, plus any associated interface definition files, plus the scripts used to control compilationand installation of the executable. However, as a special exception, the source code distributedneed not include anything that is normally distributed (in either source or binary form) with themajor components (compiler, kernel, and so on) of the operating system on which the executableruns, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designatedplace, then offering equivalent access to copy the source code from the same place counts asdistribution of the source code, even though third parties are not compelled to copy the sourcealong with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly providedunder this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program isvoid, and will automatically terminate your rights under this License. However, parties who havereceived copies, or rights, from you under this License will not have their licenses terminated solong as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothingelse grants you permission to modify or distribute the Program or its derivative works. Theseactions are prohibited by law if you do not accept this License. Therefore, by modifying ordistributing the Program (or any work based on the Program), you indicate your acceptance ofthis License to do so, and all its terms and conditions for copying, distributing or modifying theProgram or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipientautomatically receives a license from the original licensor to copy, distribute or modify the Pro-gram subject to these terms and conditions. You may not impose any further restrictions on therecipients’ exercise of the rights granted herein. You are not responsible for enforcing complianceby third parties to this License. 7.
232 16 Third-party materials and licenses
your obligations under this License and any other pertinent obligations, then as a consequenceyou may not distribute the Program at all. For example, if a patent license would not permitroyalty-free redistribution of the Program by all those who receive copies directly or indirectlythrough you, then the only way you could satisfy both it and this License would be to refrainentirely from distribution of the Program. pro-tecting the integrity of the free software distribution system, which is implemented by publiclicense practices. Many people have made generous contributions to the wide range of softwaredistributed through that system in reliance on consistent application of that system; it is up tothe author/donor to decide if he or she is willing to distribute software through any other systemand a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of therest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either bypatents or by copyrighted interfaces, the original copyright holder who places the Program underthis License may add an explicit geographical distribution limitation excluding those countries,so that distribution is permitted only in or among countries not thus excluded. In such case, thisLicense incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the GeneralPublic License from time to time. Such new versions will be similar in spirit to the presentversion, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version num-ber of this License which applies to it and “any later version”, you have the option of followingthe terms and conditions either of that version or of any later version published by the FreeSoftware Foundation. If the Program does not specify a version number of this License, you maychoose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distributionconditions are different, write to the author to ask for permission. For software which is copy-righted by the Free Software Foundation, write to the Free Software Foundation; we sometimesmake exceptions for this. Our decision will be guided by the two goals of preserving the freestatus of all derivatives of our free software and of promoting the sharing and reuse of softwaregenerally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTYFOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTH-ERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDETHE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IM-PLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABIL-ITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY ANDPERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFEC-TIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITINGWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR RE-DISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISINGOUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TOLOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOUOR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PRO-
233 16 Third-party materials and licenses
GRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITYOF SUCH DAMAGES. END OF TERMS AND CONDITIONS
234 16 Third-party materials and licenses
We call this license the “Lesser” General Public License because it does Less to protect theuser’s freedom than the ordinary General Public License. It also provides other free softwaredevelopers Less of an advantage over competing non-free programs. These disadvantages arethe reason we use the ordinary General Public License for many libraries. However, the Lesserlicense provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possibleuse of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programsmust be allowed to use the library. A more frequent case is that a free library does the same jobas widely used non-free libraries. In this case, there is little to gain by limiting the free library tofree software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greaternumber of people to use a large body of free software. For example, permission to use the GNU CLibrary in non-free programs enables many more people to use the whole GNU operating system,as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users’ freedom, it doesensure that the user of a program that is linked with the Library has the freedom and the where-withal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay closeattention to the difference between a “work based on the library” and a “work that uses thelibrary”. The former contains code derived from the library, whereas the latter must be combinedwith the library in order to run. GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRI-BUTION AND MODIFICATION 0. This License Agreement applies to any software library or other program which containsa notice placed by the copyright holder or other authorized party saying it may be distributedunder the terms of this Lesser General Public License (also called “this License”). Each licenseeis addressed as “you”. A “library” means a collection of software functions and/or data prepared so as to be conve-niently linked with application programs (which use some of those functions and data) to formexecutables. The “Library”, below, refers to any such software library or work which has been distributedunder these terms. A “work based on the Library” means either the Library or any derivativework under copyright law: that is to say, a work containing the Library or a portion of it, ei-therassociated interface definition files, plus the scripts used to control compilation and installationof the library. Activities other than copying, distribution and modification are not covered by this License;they are outside its scope. The act of running a program using the Library is not restricted, andoutput from such a program is covered only if its contents constitute a work based on the Library(independent of the use of the Library in a tool for writing it). Whether that is true depends onwhat the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library’s complete source code as youreceive it, in any medium, provided that you conspicuously and appropriately publish on eachcopy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices thatrefer to this License and to the absence of any warranty; and distribute a copy of this Licensealong with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your optionoffer warranty protection in exchange for a fee.
235 16 Third-party materials and licenses
2. You may modify your copy or copies of the Library or any portion of it, thus forming awork based on the Library, and copy and distribute such modifications or work under the termsof Section 1 above, provided that you also meet all of these conditions: a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed thefiles and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties underthe terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied byan application program that uses the facility, other than as an argument passed when the facilityis invoked, then you must make a good faith effort to ensure that, in the event an applicationdoes not supply such function or table, the facility still operates, and performs whatever part ofitssupply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that workare not derived from the Library, Library, the distribution of the whole must be on the terms of thisLicense, Library. In addition, mere aggregation of another work not based on the Library with the Library (orwith a work based on the Library) on a volume of a storage or distribution medium does notbring the other work under the scope of this License. 3. You may opt to apply the terms of the ordinary GNU General Public License instead of thisLicense to a given copy of the Library. To do this, you must alter all the notices that refer to thisLicense, so that they refer to the ordinary GNU General Public License, version 2, instead of tothis License. (If a newer version than version 2 of the ordinary GNU General Public License hasappeared, then you can specify that version instead if you wish.) Do not make any other changein these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNUGeneral Public License applies to all subsequent copies and derivative works made from thatcopy. This option is useful when you wish to copy part of the code of the Library into a program thatis not a library. 4. You may copy and distribute the Library (or a portion or derivative of it, under Section2) in object code or executable form under the terms of Sections 1 and 2 above provided thatyou accompany it with the complete corresponding machine-readable source code, which mustbe distributed under the terms of Sections 1 and 2 above on a medium customarily used forsoftware interchange. If distribution of object code is made by offering access to copy from a designated place, thenoffering equivalent access to copy the source code from the same place satisfies the requirementto distribute the source code, even though third parties are not compelled to copy the sourcealong with the object code. 5. A program that contains no derivative of any portion of the Library, but is designed to workwith the Library by being compiled or linked with it, is called a “work that uses the Library”.
236 16 Third-party materials and licenses
Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside thescope of this License. However, linking a “work that uses the Library” with the Library creates an executable that isa derivative of the Library (because it contains portions of the Library), rather than a “work thatuses the library”. The executable is therefore covered by this License. Section 6 states terms fordistribution of such executables. When a “work that uses the Library” uses material from a header file that is part of the Library,the object code for the work may be a derivative work of the Library even though the source codesmall macros and small inline functions (ten lines or less in length), then the use of the objectfile is unrestricted, regardless of whether it is legally a derivative work. (Executables containingthis object code plus portions of the Library will still fall under Section 6.) Otherwise, if the workis a derivative of the Library, you may distribute the object code for the work under the terms ofSection 6. Any executables containing that work also fall under Section 6, whether or not theyare linked directly with the Library itself. 6. As an exception to the Sections above, you may also combine or link a “work that uses theLibrary” with the Library to produce a work containing portions of the Library, and distributethat work under terms of your choice, provided that the terms permit modification of the workfor the customer’s own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it andthat the Library and its use are covered by this License. You must supply a copy of this License.If the work during execution displays copyright notices, you must include the copyright noticefor the Library among them, as well as a reference directing the user to the copy of this License.Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code forthe Library including whatever changes were used in the work (which must be distributed underSections 1 and 2 above); and, if the work is an executable linked with the Library, with thecomplete machine-readable “work that uses the Library”, as object code and/or source code, sothat the user can modify the Library and then relink to produce a modified executable containingthe modified Library. (It is understood that the user who changes the contents of definitionsfiles in the Library will not necessarily be able to recompile the application to use the modifieddefinitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanismis one that (1) uses at run time a copy of the library already present on the user’s computersystem, rather than copying library functions into the executable, and (2) will operate properlywith a modified version of the library, if the user installs one, as long as the modified version isinterface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same userthe materials specified in Subsection 6a, above, for a charge no more than the cost of performingthis distribution. d) If distribution of the work is made by offering access to copy from a designated place, offerequivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have alreadysent this user a copy. For an executable, the required form of the “work that uses the Library” must include anydata and utility programs needed for reproducing the executable from it. However, as a specialexception, 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 theoperating system on which the executable runs, unless that component itself accompanies theexecutable.
237 16 Third-party materials and licenses
It may happen that this requirement contradicts the license restrictions of other proprietarylibraries that do not normally accompany the operating system. Such a contradiction means youcannot use both them and the Library together in an executable that you distribute. 7. You may place library facilities that are a work based on the Library side-by-side in a singlelibrary together with other library facilities not covered by this License, and distribute such acombined library, provided that the separate distribution of the work based on the Library andof the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncom-bined with any other library facilities. This must be distributed under the terms of the Sectionsabove. b) Give prominent notice with the combined library of the fact that part of it is a work basedon the Library, and explaining where to find the accompanying uncombined form of the samework. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expresslyprovided under this License. Any attempt otherwise to copy, modify, sublicense, link with, ordistribute the Library is void, and will automatically terminate your rights under this License.However, parties who have received copies, or rights, from you under this License will not havetheir licenses terminated so long as such parties remain in full compliance. 9. You are not required to accept this License, since you have not signed it. However, nothingelse grants you permission to modify or distribute the Library or its derivative works. Theseactions are prohibited by law if you do not accept this License. Therefore, by modifying ordistributing the Library (or any work based on the Library), you indicate your acceptance ofthis License to do so, and all its terms and conditions for copying, distributing or modifying theLibrary or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipientautomatically receives a license from the original licensor to copy, distribute, link with or modifythe Library subject to these terms and conditions. You may not impose any further restrictionson the recipients’ exercise of the rights granted herein. You are not responsible for enforcingcompliance by third parties with this License. 11.your obligations under this License and any other pertinent obligations, then as a consequenceyou may not distribute the Library at all. For example, if a patent license would not permitroyalty-free redistribution of the Library by all those who receive copies directly or indirectlythrough you, then the only way you could satisfy both it and this License would be to refrainentirely from distribution of the Library. protect-ing the integrity of the free software distribution system which is implemented by public licensepractices. Many people have made generous contributions to the wide range of software dis-tributed through that system in reliance on consistent application of that system; it is up to theauthor/donor to decide if he or she is willing to distribute software through any other systemand a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of therest of this License. 12. If the distribution and/or use of the Library is restricted in certain countries either bypatents or by copyrighted interfaces, the original copyright holder who places the Library underthis License may add an explicit geographical distribution limitation excluding those countries,
238 16 Third-party materials and licenses
so that distribution is permitted only in or among countries not thus excluded. In such case, thisLicense incorporates the limitation as if written in the body of this License. 13. The Free Software Foundation may publish revised and/or new versions of the LesserGeneral Public License from time to time. Such new versions will be similar in spirit to thepresent version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version numberof this License which applies to it and “any later version”, you have the option of following theterms and conditions either of that version or of any later version published by the Free SoftwareFoundation. If the Library does not specify a license version number, you may choose any versionever published by the Free Software Foundation. 14. If you wish to incorporate parts of the Library into other free programs whose distributionconditions are incompatible with these, write to the author to ask for permission. For softwarewhich is copyrighted by the Free Software Foundation, write to the Free Software Foundation; wesometimes make exceptions for this. Our decision will be guided by the two goals of preservingthe free status of all derivatives of our free software and of promoting the sharing and reuse ofsoftware generally. NO WARRANTY 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FORTHE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHER-WISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDETHE LIBRARY “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PER-FORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOUASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITINGWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDIS-TRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUD-ING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OFTHE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OFDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRDPARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVENIF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCHDAMAGES. END OF TERMS AND CONDITIONS
239 16 Third-party materials and licenses
1.7. “Larger Work” means a work which combines Covered Code or portions thereof with codenot governed by the terms of this License. 1.8. “License” means this document. 1.8.1. “Licensable” means having the right to grant, to the maximum extent possible, whetherat the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein. 1.9. “Modifications” means any addition to or deletion from the substance or structure ofeither the Original Code or any previous Modifications. When Covered Code is released as aseries of files, a Modification is:, subjectfirst distributes Original Code under the terms of this License. (d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for code that Youdelete from the Original Code; 2) separate from the Original Code; or 3) for infringementscaused by: i) the modification of the Original Code or ii) the combination of the Original Codewith other software or devices. 2.2. Contributor Grant. Subject to third party intellectual property claims, each Contributorhereby Patent Claims infringed by the making, using, or selling of Modifications made bythat Contributor either alone and/or in combination with its Contributor Version (or portions
240 16 Third-party materials and licenses
of such combination), to make, use, sell, offer for sale, have made, and/or otherwise disposeof: 1) Modifications made by that Contributor (or portions thereof); and 2) the combinationof Modifications made by that Contributor with its Contributor Version (or portions of suchcombination). (c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor firstmakes Commercial Use of the Covered Code. (d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for any code thatContributor has deleted from the Contributor Version; 2) separate from the Contributor Version;3) for infringements caused by: i) third party modifications of Contributor Version or ii) thecombination of Modifications made by that Contributor with other software (except as part ofthe Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Codein the absence of Modifications made by that Contributor. 3. Distribution Obligations. 3.1. Application of License. The Modifications which You create or to which You contributeare governed by the terms of this License, including without limitation Section 2.2. The SourceCode version of Covered Code may be distributed only under the terms of this License or afuture version of this License released under Section 6.1, and You must include a copy of thisLicense with every copy of the Source Code You distribute. You may not offer or impose anyterms on any Source Code version that alters or restricts the applicable version of this License orthe recipients’ rights hereunder. However, You may include an additional document offering theadditional rights described in Section 3.5. 3.2. Availability of Source Code. Any Modification which You create or to which You con-tribute must be made available in Source Code form under the terms of this License either on thesame media as an Executable version or via an accepted Electronic Distribution Mechanism toanyone to whom you made an Executable version available; and if made available via ElectronicDistribution Mechanism, must remain available for at least twelve (12) months after the date itinitially became available, or at least six (6) months after a subsequent version of that partic-ular Modification has been made available to such recipients. You are responsible for ensuringthat the Source Code version remains available even if the Electronic Distribution Mechanism ismaintained by a third party. 3.3. Description of Modifications. You must cause all Covered Code to which You contributeto contain a file documenting the changes You made to create that Covered Code and the date ofany change. You must include a prominent statement that the Modification is derived, directlyor indirectly, from Original Code provided by the Initial Developer and including the name ofthe Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version orrelated documentation in which You
241 16 Third-party materials and licenses
name. Youmust make it absolutely clear than any such warranty, support, indemnity or liability obligationis offered by You alone, and You hereby agree to indemnify the Initial Developer and everyContributor for any liability incurred by the Initial Developer or such Contributor as a result ofwarranty, support, indemnity or liability terms You offer. 3.6. Distribution of Executable Versions. You may distribute Covered Code in Executableform only if the requirements of Section 3.1-3.5 have been met for that Covered Code, andif You include a notice stating that the Source Code version of the Covered Code is availableunder the terms of this License, including a description of how and where You have fulfilledthe obligations of Section 3.2. The notice must be conspicuously included in any notice in anExecutable version, related documentation or collateral in which You describe recipients’ rightsrelating to the Covered Code. You may distribute the Executable version of Covered Code orownership rights under a license of Your choice, which may contain terms different from thisLicense, provided that You are in compliance with the terms of this License and that the licensefor the Executable version does not attempt to limit or alter the recipient’s rights in the SourceCode version from the rights set forth in this License. If You distribute the Executable versionunder a different license You must make it absolutely clear that any terms which differ from thisLicense are offered by You alone, not by the Initial Developer or any Contributor. You herebyagree to indemnify the Initial Developer and every Contributor for any liability incurred by theInitial 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 codenot governed by the terms of this License and distribute the Larger Work as a single product. Insuch a case, You must make sure the requirements of this License are fulfilled for the CoveredCode. 4. Inability to Comply Due to Statute or Regulation.If it is impossible for You to comply withany 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 max-imum extent possible; and (b) describe the limitations and the code they affect. Such descriptionmust be included in the LEGAL file described in Section 3.4 and must be included with all dis-tributions of the Source Code. Except to the extent prohibited by statute or regulation, suchdescription must be sufficiently detailed for a recipient of ordinary skill to be able to understandit. 5. Application of this License. This License applies to code to which the Initial Developer hasattached the notice in Exhibit A and to related Covered Code. 6. Versions of the License. 6.1. New Versions. Netscape Communications Corporation (“Netscape”) may publish revisedand/or new versions of the License from time to time. Each version will be given a distinguishingversion number. 6.2. Effect of New Versions. Once Covered Code has been published under a particular versionof the License, You may always continue to use it under the terms of that version. You mayalso choose to use such Covered Code under the terms of any subsequent version of the Licensepublished by Netscape. No one other than Netscape has the right to modify the terms applicableto Covered Code created under this License. 6.3. Derivative Works. If You create or use a modified version of this License (which youmay only do in order to apply it to code which is not already Covered Code governed by this Li-cense), You must (a) rename Your license so that the phrases “Mozilla”, “MOZILLAPL”, “MOZPL”,“Netscape”, “MPL”, “NPL” or any confusingly similar phrase do not appear in your license (ex-cept to note that your license differs from this License) and (b) otherwise make it clear that Yourversion of the license contains terms which differ from the Mozilla Public License and Netscape
242 16 Third-party materials and licenses
Public License. (Filling in the name of the Initial Developer, Original Code or Contributor inthe notice described in Exhibit A shall not of themselves be deemed to be modifications of thisLicense.) 7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS” BASIS, WITHOUT WAR-RANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION,WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR APARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY ANDPERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVEDEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIB-UTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THISDISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USEOF 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 failto comply with terms herein and fail to cure such breach within 30 days of becoming aware ofthe breach. All sublicenses to the Covered Code which are properly granted shall survive anytermination of this License. Provisions which, by their nature, must remain in effect beyond thetermination of this License shall survive. 8.2. If You initiate litigation by asserting a patent infringement claim (excluding declaratoryjudgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributoragainst whom You file such action is referred to as “Participant”) alleging that: (a) such Participant’s Contributor Version directly or indirectly infringes any patent, then anyand all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this Licenseshall, upon 60 days notice from Participant terminate prospectively, unless if within 60 daysafter receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeablereasonable royalty for Your past and future use of Modifications made by such Participant, or (ii)withdraw Your litigation claim with respect to the Contributor Version against such Participant.If within 60 days of notice, a reasonable royalty and payment arrangement are not mutuallyagreed upon in writing by the parties or the litigation claim is not withdrawn, the rights grantedby Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration ofthe 60 day notice period specified above. (b) any software, hardware, or device, other than such Participant’s Contributor Version, di-rectly or indirectly infringes any patent, then any rights granted to You by such Participant underSections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, dis-tributed, or had made, Modifications made by that Participant. 8.3. If You assert a patent infringement claim against Participant alleging that such Partici-pant’s Contributor Version directly or indirectly infringes any patent where such claim is resolved(such as by license or settlement) prior to the initiation of patent infringement litigation, thenthe reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shallbe taken into account in determining the amount or value of any payment or license. 8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agree-ments (excluding distributors and resellers) which have been validly granted by You or anydistributor hereunder prior to termination shall survive termination. 9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THE-ORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU,THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVEREDCODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANYINDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER IN-CLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE,COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAM-AGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITYOF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR
243 16 Third-party materials and licenses
DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY’S NEGLIGENCE TO THE EX-TENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT AL-LOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SOTHIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered Code is a “commercial item,“ as that termforth herein. 11. MISCELLANEOUS. This License represents the complete agreement concerning subjectmatter hereof. If any provision of this License is held to be unenforceable, such provision shallbe reformed only to the extent necessary to make it enforceable. This License shall be governedby California law provisions (except to the extent applicable law, if any, provides otherwise),excluding its conflict-of-law provisions. With respect to disputes in which at least one party isa citizen of, or an entity chartered or registered to do business in the United States of America,any litigation relating to this License shall be subject to the jurisdiction of the Federal Courtsof the Northern District of California, with venue lying in Santa Clara County, California, withthe losing party responsible for costs, including without limitation, court costs and reasonableattorneys’ fees and expenses. The application of the United Nations Convention on Contracts forthe International Sale of Goods is expressly excluded. Any law or regulation which provides thatthe language of a contract shall be construed against the drafter shall not apply to this License. 12. RESPONSIBILITY FOR CLAIMS. As between Initial Developer and the Contributors, eachparty is responsible for claims and damages arising, directly or indirectly, out of its utilization ofrights under this License and You agree to work with Initial Developer and Contributors to dis-tribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemedto constitute any admission of liability. 13. MULTIPLE-LICENSED CODE. Initial Developer may designate portions of the CoveredCode as “Multiple-Licensed”. “Multiple-Licensed” means that the Initial Developer permits youtoLicense at Software distributed under the License is distributed on an “AS IS” basis, WITHOUT WAR-RANTY OF ANY KIND, either express or implied. See the License for the specific language gov-erning rights and limitations under the License. The Original Code is ______________________________________. The Initial Developer of the Original Code is ________________________. Portions createdby ______________________ are Copyright (C) ______ _______________________. All RightsReserved. Contributor(s): ______________________________________. Alternatively, the contents of this file may be used under the terms of the _____ license (the“[___] License”), in which case the provisions of [______] License are applicable instead of thoseabove. If you wish to allow use of your version of this file only under the terms of the [____]License and not to allow others to use your version of this file under the MPL, indicate yourdecision by deleting the provisions above and replace them with the notice and other provisionsrequired by the [___] License. If you do not delete the provisions above, a recipient may useyour version of this file under either the MPL or the [___] License.“ [NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the SourceCode files of the Original Code. You should use the text of this Exhibit A rather than the textfound in the Original Code Source Code for Your Modifications.]
244 16 Third-party materials and licenses
245 16 Third-party materials and licenses
This library is free for commercial and non-commercial use as long as the following conditionsare adhered to. The following conditions apply to all code found in this distribution, be it theRC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included withthis distribution is covered by the same copyright terms except that the holder is Tim Hudson(tjh@cryptsoft.com). Copyright remains Eric Young’s, and as such any Copyright notices in the code are not to beremoved. If this package is used in a product, Eric Young should be given attribution as theauthor of the parts of the library used. This can be in the form of a textual message at programstartup or in documentation (online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permittedprovided that the following conditions are met: 1. Redistributions of source code must retain the copyright notice, this list of conditions andthe following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of con-ditions and the following disclaimer in the documentation and/or other materials provided withthe distribution. 3. All advertising materials mentioning features or use of this software must display the fol-lowing acknowledgement: “This product includes cryptographic software written by Eric Young(eay@cryptsoft.com)“ The word ’cryptographic’ can be left out if the routines from the librarybeing used are not cryptographic related :-). 4. If you include any Windows specific code (or a derivative thereof) from the apps direc-tory (application code) you must include an acknowledgement: “This product includes softwarewritten by Tim Hudson (tjh@cryptsoft.com)“ THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MER-CHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENTSHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDEN-TAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITEDTO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROF-ITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTH-ERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OFTHE POSSIBILITY OF SUCH DAMAGE. The licence and distribution terms for any publicly available version or derivative of this codecannot be changed. i.e. this code cannot simply be copied and put under another distributionlicence [including the GNU Public Licence.]
246 16 Third-party materials and licenses
247 16 Third-party materials and licenses
1. Redistributions of source code must retain the above copyright notice, this list of conditionsand the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of con-ditions and the following disclaimer in the documentation and/or other materials provided withthe distribution. 3. The name of the author may not be used to endorse or promote products derived from thissoftware without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MER-CHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENTSHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEM-PLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENTOF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS IN-TERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CON-TRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OFSUCH DAMAGE.
248 16 Third-party materials and licenses
DANIEL VEILLARD BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHERIN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CON-NECTION 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 advertisingor otherwise to promote the sale, use or other dealings in this Software without prior writtenauthorization from him. Licence for libexslt: Copyright (C) 2001-2002 Thomas Broyer, Charlie Bozeman and Daniel Veillard. All RightsReserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this softwareand associated documentation files (the “Software”), to deal in the Software without restric-tion, including without limitation the rights to use, copy, modify, merge, publish, distribute,sublicense, and/or sell copies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or sub-stantial portions of the Software. THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FIT-NESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN ANACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNEC-TION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of the authors shall not be used in advertisingor otherwise to promote the sale, use or other dealings in this Software without prior writtenauthorization from him.
249 16 Third-party materials and licenses, sub-ject now or hereafter owned or controlled by Initial Developer, to make, havemade, use and sell (“offer to sell and import”) the Original Code, Modifications, or portionsthereof, but solely to the extent that any such patent is reasonably necessary to enable You toutilize, alone or in combination with other software, the Original Code, Modifications, or anycombination or portions thereof. (c) (d) 2.2. Contributor Grant. Subject to third party intellectual property claims, each Contributor hereby patents now or hereafter owned or controlled by Contributor, to make, have made,use and sell (“offer to sell and import”) the Contributor Version (or portions thereof), but solelyto the extent that any such patent is reasonably necessary to enable You to utilize, alone or incombination with other software, the Contributor Version (or portions thereof). (c) (d) 3 DISTRIBUTION OBLIGATIONS. 3.1. Application of License. The Modifications which You create or to which You contribute are governed by the termsof this License, including without limitation Section 2.2. The Source Code version of Covered
250 16 Third-party materials and licenses
Code may be distributed only under the terms of this License or a future version of this Licensereleased under Section 6.1, and You must include a copy of this License with every copy of theSource Code You distribute. You may not offer or impose any terms on any Source Code versionthat alters or restricts the applicable version of this License or the recipients’ rights hereunder.However, You may include an additional document offering the additional rights described inSection 3.5. 3.2. Availability of Source Code. Any Modification created by You will be provided to the Initial Developer in Source Code formand are subject to the terms of the License. 3.3. Description of Modifications. You must cause all Covered Code to which You contribute to contain a file documenting thechanges You made to create that Covered Code and the date of any change. You must include aprominent statement that the Modification is derived, directly or indirectly, from Original Codeprovided by the Initial Developer and including the name of the Initial Developer in (a) theSource Code, and (b) in any notice in an Executable version or related documentation in whichYou. (c) Representations. Contributor represents that, except as disclosed pursuant to Section3.4(a) above, Contributor believes that Contributor’s Modifications are Contributor’s originalcreation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License.name. 3.6. Distribution of Executable Versions. You may distribute Covered Code in Executable formonly if the requirements of Section 3.1-3.5 have been met for that Covered Code. You maydistribute the Executable version of Covered Code or ownership rights under a license of Yourchoice, which may contain terms different from this License, provided that You are in compliancewith the terms of this License and that the license for the Executable version does not attemptto limit or alter the recipient’s rights in the Source Code version from the rights set forth inthis License. If You distribute the Executable version under a different license You must make itabsolutely clear that any terms which differ from this License are offered by You alone, not by theInitial Developer or any Contributor. If you distribute executable versions containing CoveredCode as part of a product, you must reproduce the notice in Exhibit B in the documentationand/or other materials provided with the product. 3.7. Larger Works. You may create a Larger Work by combining Covered Code with other codenot governed by the terms of this License and distribute the Larger Work as a single product. In
251 16 Third-party materials and licenses
such a case, You must make sure the requirements of this License are fulfilled for the CoveredCode. 3.8. Restrictions. You may not remove any product identification, copyright, proprietary no-tices 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 someor all of the Covered Code due to statute, judicial order, or regulation then You must: (a) complywith the terms of this License to the maximum extent possible; and (b) describe the limitationsand the code they affect. Such description must be included in the LEGAL file described inSection 3.4 and must be included with all distributions of the Source Code. Except to the extentprohibited by statute or regulation, such description must be sufficiently detailed for a recipientof ordinary skill to be able to understand it. 5 APPLICATION OF THIS LICENSE. This License applies to code to which the Initial Developer has attached the notice in ExhibitA and to related Covered Code. 6 VERSIONS OF THE LICENSE. 6.1. New Versions. Grantor may publish revised and/or new versions of the License from time to time. Eachversion will be given a distinguishing version number. 6.2. Effect of New Versions. Once Covered Code has been published under a particular version of the License, You mayalways continue to use it under the terms of that version. You may also choose to use suchCovered Code under the terms of any subsequent version of the License. 6.3. Derivative Works. If You create or use a modified version of this License (which you may only do in order to applyit to code which is not already Covered Code governed by this License), You must (a) renameYour license so that the phrase “gSOAP” or any confusingly similar phrase do not appear in yourlicense (except to note that your license differs from this License) and (b) otherwise make itclear that Your version of the license contains terms which differ from the gSOAP Public License.(Filling in the name of the Initial Developer, Original Code or Contributor in the notice describedin Exhibit A shall not of themselves be deemed to be modifications of this License.) 7 DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN “AS IS” BASIS, WITHOUT WAR-RANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING, WITHOUTLIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY, OF FITNESS FOR A PARTIC-ULAR PURPOSE, NONINFRINGEMENT OF THIRD PARTY INTELLECTUAL PROPERTY RIGHTS,AND ANY WARRANTY THAT MAY ARISE BY REASON OF TRADE USAGE, CUSTOM, OR COURSEOF DEALING. WITHOUT LIMITING THE FOREGOING, YOU ACKNOWLEDGE THAT THE SOFT-WARE IS PROVIDED “AS IS” AND THAT THE AUTHORS DO NOT WARRANT THE SOFTWAREWILL RUN UNINTERRUPTED OR ERROR FREE. LIMITED LIABILITY THE ENTIRE RISK ASTO RESULTS AND PERFORMANCE OF THE SOFTWARE IS ASSUMED BY YOU. UNDER NOCIRCUMSTANCES WILL THE AUTHORS BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDEN-TAL, EXEMPLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND OR NATURE WHATSOEVER,WHETHER BASED ON CONTRACT, WARRANTY, TORT (INCLUDING NEGLIGENCE), STRICTLIABILITY 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 ORIF SUCH DAMAGE COULD HAVE BEEN REASONABLY FORESEEN, AND NOTWITHSTANDINGANY FAILURE OF ESSENTIAL PURPOSE OF ANY EXCLUSIVE REMEDY PROVIDED. SUCH LIMI-TATION ON DAMAGES INCLUDES, BUT IS NOT LIMITED TO, DAMAGES FOR LOSS OF GOOD-WILL, LOST PROFITS, LOSS OF DATA OR SOFTWARE, WORK STOPPAGE, COMPUTER FAILUREOR MALFUNCTION OR IMPAIRMENT OF OTHER GOODS. IN NO EVENT WILL THE AUTHORSBE LIABLE FOR THE COSTS OF PROCUREMENT OF SUBSTITUTE SOFTWARE OR SERVICES.YOU ACKNOWLEDGE THAT THIS SOFTWARE IS NOT DESIGNED FOR USE IN ON-LINE EQUIP-
252 16 Third-party materials and licenses
253 16 Third-party materials and licenses