who wishes to control VirtualBox programmatically. We chose the name “Main API” to differentiate it from other programming interfaces of VirtualBox that may be publicly accessible. With the Main API, you need is a programming language with a toolkit that can parse WSDL and generate client wrapper code from it. We describe this further in chapter 6, Using the raw web service with any language, page xxxvi service; extensive support even with other languages (C++, .NET, PHP, Perl and others) Con: Usable from languages where COM bridge available (most languages on Windows platform, Python and C++ on other

who wishes to control VirtualBox programmatically. We chose the name “Main API” to differentiate it from other programming interfaces of VirtualBox that may be publicly accessible. With the Main API, you need is a programming language with a toolkit that can parse WSDL and generate client wrapper code from it. We describe this further in chapter 2.2, Using the raw web service with any language, page 10 service; extensive support even with other languages (C++, .NET, PHP, Perl and others) Con: Usable from languages where COM bridge available (most languages on Windows platform, Python and C++ on other

who wishes to control VirtualBox programmatically. We chose the name “Main API” to differentiate it from other programming interfaces of VirtualBox that may be publicly accessible. With the Main API, you need is a programming language with a toolkit that can parse WSDL and generate client wrapper code from it. We describe this further in chapter 2.2, Using the raw web service with any language, page 36 service; extensive support even with other languages (C++, .NET, PHP, Perl and others) Con: Usable from languages where COM bridge available (most languages on Windows platform, Python and C++ on other

who wishes to control VirtualBox programmatically. We chose the name “Main API” to differentiate it from other programming interfaces of VirtualBox that may be publicly accessible. With the Main API, you need is a programming language with a toolkit that can parse WSDL and generate client wrapper code from it. We describe this further in chapter 6, Using the raw web service with any language, page xxxvi service; extensive support even with other languages (C++, .NET, PHP, Perl and others) Con: Usable from languages where COM bridge available (most languages on Windows platform, Python and C++ on other

who wishes to control VirtualBox programmatically. We chose the name “Main API” to differentiate it from other programming interfaces of VirtualBox that may be publicly accessible. With the Main API, you need is a programming language with a toolkit that can parse WSDL and generate client wrapper code from it. We describe this further in chapter 2.2, Using the raw web service with any language, page 10 service; extensive support even with other languages (C++, .NET, PHP, Perl and others) Con: Usable from languages where COM bridge available (most languages on Windows platform, Python and C++ on other

Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3 Installing on Linux hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3.1 Prerequisites . . . vboxusers group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.5 Starting VirtualBox on Linux . . . . . . . . . . . . . . . . . . . . . . . . 36 2.4 Installing on Solaris hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 3.10.2 Implementation notes for Windows and Linux hosts . . . . . . . . . . . 51 3.11 Shared folders . . . . . . . . . . . . . . . . . . . . . . .

Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3 Installing on Linux hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3.1 Prerequisites . . . vboxusers group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.5 Starting VirtualBox on Linux . . . . . . . . . . . . . . . . . . . . . . . . 36 2.4 Installing on Solaris hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 3.10.2 Implementation notes for Windows and Linux hosts . . . . . . . . . . . 51 3.11 Shared folders . . . . . . . . . . . . . . . . . . . . . . .

Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3 Installing on Linux hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 2.3.1 Prerequisites . . . vboxusers group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 2.3.5 Starting VirtualBox on Linux . . . . . . . . . . . . . . . . . . . . . . . . 36 2.4 Installing on Solaris hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 3.10.2 Implementation notes for Windows and Linux hosts . . . . . . . . . . . 51 3.11 Shared folders . . . . . . . . . . . . . . . . . . . . . . .

Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.3 Installing on Linux hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 2.3.1 Prerequisites . . . vboxusers group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 2.3.5 Starting VirtualBox on Linux . . . . . . . . . . . . . . . . . . . . . . . . 35 2.4 Installing on Solaris hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 3.10.2 Implementation notes for Windows and Linux hosts . . . . . . . . . . . 49 3.11 Shared folders . . . . . . . . . . . . . . . . . . . . . . .

Unattended installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3 Installing on Linux hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 2.3.1 Prerequisites . . . vboxusers group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 2.3.5 Starting VirtualBox on Linux . . . . . . . . . . . . . . . . . . . . . . . . 39 2.4 Installing on Solaris hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 3.10.2 Implementation notes for Windows and Linux hosts . . . . . . . . . . . 54 3.11 Shared folders . . . . . . . . . . . . . . . . . . . . . . .