From: John Ferlan
The naming of the functions present in the library is usually - made of a prefix describing the object associated to the function + composed by a prefix describing the object associated to the function and a verb describing the action on that object.
-For each first class object you will find apis +
For each first class object you will find APIs for the following actions:
virConnectListDomains,
- virConnectNumOfDomains,
- virConnectListNetworks,
- virConnectListStoragePools, etc.virNodeGetInfo,
- virDomainGetInfo,
- virStoragePoolGetInfo,
- virStorageVolGetInfo.virConnectGetType,
- virDomainGetMaxMemory,
- virDomainSetMemory,
- virDomainGetVcpus,
- virStoragePoolSetAutostart,
- virNetworkGetBridgeName, etc.Used to perform lookups on objects by some type of identifier, + such as:
+virDomainLookupByIDvirDomainLookupByNamevirDomainLookupByUUIDvirDomainLookupByUUIDStringUsed to enumerate a set of object available to an given + hypervisor connection such as:
+virConnectListDomainsvirConnectNumOfDomainsvirConnectListNetworksvirConnectListStoragePoolsGeneric accessor providing a set of generic information about an + object, such as:
+virNodeGetInfovirDomainGetInfovirStoragePoolGetInfovirStorageVolGetInfoSpecific accessors used to query or modify data for the given object, + such as:
+virConnectGetTypevirDomainGetMaxMemoryvirDomainSetMemoryvirDomainGetVcpusvirStoragePoolSetAutostartvirNetworkGetBridgeNameUsed to create and start objects. The ...CreateXML APIs will create + the object based on an XML description, while the ...Create APIs will + create the object based on existing object pointer, such as:
+virDomainCreatevirDomainCreateXMLvirNetworkCreatevirNetworkCreateXMLUsed to shutdown or deactivate and destroy objects, such as:
+virDomainDestroyvirNetworkDestroyvirStoragePoolDestroyFor more in-depth details of the storage related APIs see the storage management page.