Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1 Modularity: the building blocks of VirtualBox VirtualBox is cleanly visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1 Modularity: the building blocks of VirtualBox VirtualBox is cleanly visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is cleanly visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of API”: the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships

Devel- opment Kit (SDK) contains all the documentation and interface files that are needed to write code that interacts with VirtualBox. 1.1 Modularity: the building blocks of VirtualBox VirtualBox is cleanly visualized like in the picture below: The orange area represents code that runs in kernel mode, the blue area represents userspace code. At the bottom of the stack resides the hypervisor – the core of API”: the web service or COM/XPCOM There are several ways in which the Main API can be called by other code: 1. VirtualBox comes with a web service that maps nearly the entire Main API. The web ser- vice ships