Changes between Version 1 and Version 2 of VirtualBox_architecture

Timestamp:

Feb 9, 2007 1:07:11 PM (17 years ago)

Author:

umoeller

Comment:

--

VirtualBox_architecture

@@ -23 +23 @@
  1. '''Client/server architecture.''' All aspects of !VirtualBox and the VMs that are running can be controlled with a simple, yet powerful, COM/XPCOM API. For example, there is a command-line utility called `VBoxManage` that allows you to control VMs just like the GUI does (in fact, many of the more sophisticated operations are not yet supported by the GUI). You can, for example, start a VM from the GUI (by clicking on the "Start" button) and stop it again from `VBoxManage`. 
 
- This is why the service process (`VBoxSVC`) is needed: it acts as a librarian of what VMs are running and what states their in. 
+ This is why the service process (`VBoxSVC`) is needed: it keeps track of which VMs are running and what state they're in. 
 
  2. '''Frontend/backend architecture.''' The guts of !VirtualBox -- everything that makes x86 virtualization complicated and messy -- are hidden in a shared library, `VBoxVMM.dll`, or `VBoxVMM.so` on Linux. This can be considered a "backend", or black box, that is static, and it is relatively easy to write another frontend without having to mess with the gory details of x86 virtualization. So, as an example, if you don't like the fact that the GUI is a Qt application, you can easily write a different frontend (say, using GTK).