diff --git a/docs/api.html.in b/docs/api.html.in index 9855b39cde..51d6527773 100644 --- a/docs/api.html.in +++ b/docs/api.html.in @@ -161,14 +161,31 @@
For more in-depth details of the storage related APIs see the storage management page.
-Drivers are the basic building block for libvirt functionality
+ to support the capability to handle specific hypervisor driver calls.
+ Drivers are discovered and registered during connection processing as
+ part of the virInitialize
API. Each driver
+ has a registration API which loads up the driver specific function
+ references for the libvirt APIs to call. The following is a simplistic
+ view of the hypervisor driver mechanism. Consider the stacked list of
+ drivers as a series of modules that can be plugged into the architecture
+ depending on how libvirt is configured to be built.
-
The driver architecture is also used to support other virtualization + components such as storage, storage pools, host device, networking, + network interfaces, and network filters.
+See the libvirt drivers page for more + information on hypervisor and storage specific drivers.
+Not all drivers support every virtualization function possible. + The libvirt API support matrix lists + the various functions and support found in each driver by the version + support was added into libvirt. +
+