of the hypervisor, additional internal modules provide extra functionality. For example, the RDP server, which can deliver the graphical output of a VM remotely to an RDP client, is a separate module that web ser- vice ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described 1. The VirtualBox web service (the “server”): this is the vboxwebsrv executable shipped with VirtualBox. Once you start this executable (which acts as a HTTP server on a specific TCP/IP port), clients

of the hypervisor, additional internal modules provide extra functionality. For example, the RDP server, which can deliver the graphical output of a VM remotely to an RDP client, is a separate module that web ser- vice ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described 1. The VirtualBox web service (the “server”): this is the vboxwebsrv executable shipped with VirtualBox. Once you start this executable (which acts as a HTTP server on a specific TCP/IP port), clients

of the hypervisor, additional internal modules provide extra functionality. For example, the RDP server, which can deliver the graphical output of a VM remotely to an RDP client, is a separate module that web ser- vice ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described 1. The VirtualBox web service (the “server”): this is the vboxwebsrv executable shipped with VirtualBox. Once you start this executable (which acts as a HTTP server on a specific TCP/IP port), clients

of the hypervisor, additional internal modules provide extra functionality. For example, the RDP server, which can deliver the graphical output of a VM remotely to an RDP client, is a separate module that web ser- vice ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described 1. The VirtualBox web service (the “server”): this is the vboxwebsrv executable shipped with VirtualBox. Once you start this executable (which acts as a HTTP server on a specific TCP/IP port), clients

of the hypervisor, additional internal modules provide extra functionality. For example, the RDP server, which can deliver the graphical output of a VM remotely to an RDP client, is a separate module that web ser- vice ships in a stand-alone executable (vboxwebsrv) that, when running, acts as an HTTP server, accepts SOAP connections and processes them. Since the entire web service API is publicly described 1. The VirtualBox web service (the “server”): this is the vboxwebsrv executable shipped with VirtualBox. Once you start this executable (which acts as an HTTP server on a specific TCP/IP port), clients

116 7.1.2 VBoxHeadless, the Remote Desktop Server . . . . . . . . . . . . . . . . 117 7.1.3 Step by Step: Creating a Virtual Machine on a Headless Server . . . . . 119 7.1.4 Remote USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 7.1.7 Multiple Connections to the VRDP Server . . . . . . . . . . . . . . . . . 123 7.1.8 Multiple Remote Monitors . . . . . . . . . . . . . the Address of a NAT Network Interface . . . . . . . . . . . 253 9.8.2 Configuring the Boot Server (Next Server) of a NAT Network Interface . 253 9.8.3 Tuning TCP/IP Buffers for NAT . . . . . . . . . .

Supported guest operating systems . . . . . . . . . . . . . . . . . . . . . . . . . 42 3.1.1 Mac OS X Server guests . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 3.1.2 64-bit guests . . . . . . 95 7.1.2 VBoxHeadless, the remote desktop server . . . . . . . . . . . . . . . . . 96 7.1.3 Step by step: creating a virtual machine on a headless server . . . . . . 97 7.1.4 Remote USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 7.1.7 Multiple connections to the VRDP server . . . . . . . . . . . . . . . . . 101 7.1.8 Multiple remote monitors . . . . . . . . . . . . .

121 7.1.2 VBoxHeadless, the Remote Desktop Server . . . . . . . . . . . . . . . . 122 7.1.3 Step by Step: Creating a Virtual Machine on a Headless Server . . . . . 124 7.1.4 Remote USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 7.1.7 Multiple Connections to the VRDP Server . . . . . . . . . . . . . . . . . 128 7.1.8 Multiple Remote Monitors . . . . . . . . . . . . . the Address of a NAT Network Interface . . . . . . . . . . . 259 9.8.2 Configuring the Boot Server (Next Server) of a NAT Network Interface . 259 9.8.3 Tuning TCP/IP Buffers for NAT . . . . . . . . . .

121 7.1.2 VBoxHeadless, the Remote Desktop Server . . . . . . . . . . . . . . . . 122 7.1.3 Step by Step: Creating a Virtual Machine on a Headless Server . . . . . 124 7.1.4 Remote USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 7.1.7 Multiple Connections to the VRDP Server . . . . . . . . . . . . . . . . . 128 7.1.8 Multiple Remote Monitors . . . . . . . . . . . . . the Address of a NAT Network Interface . . . . . . . . . . . 259 9.8.2 Configuring the Boot Server (Next Server) of a NAT Network Interface . 259 9.8.3 Tuning TCP/IP Buffers for NAT . . . . . . . . . .

121 7.1.2 VBoxHeadless, the Remote Desktop Server . . . . . . . . . . . . . . . . 122 7.1.3 Step by Step: Creating a Virtual Machine on a Headless Server . . . . . 124 7.1.4 Remote USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 7.1.7 Multiple Connections to the VRDP Server . . . . . . . . . . . . . . . . . 128 7.1.8 Multiple Remote Monitors . . . . . . . . . . . . . the Address of a NAT Network Interface . . . . . . . . . . . 259 9.8.2 Configuring the Boot Server (Next Server) of a NAT Network Interface . 259 9.8.3 Tuning TCP/IP Buffers for NAT . . . . . . . . . .