提交 25b133e7 编写于 作者: M Michal Novotny 提交者: Eric Blake

api-docs: Fix description of virConnectGetType() API function

This fixes the description of virConnectGetType() API function in
API documentation to match the real functionality that it can be
used to get driver name, and provide a hint on how to learn about
full capabilities.
Signed-off-by: NMichal Novotny <minovotn@redhat.com>
Signed-off-by: NEric Blake <eblake@redhat.com>
上级 cf83adfb
...@@ -1581,7 +1581,11 @@ virConnectSupportsFeature(virConnectPtr conn, int feature) ...@@ -1581,7 +1581,11 @@ virConnectSupportsFeature(virConnectPtr conn, int feature)
* virConnectGetType: * virConnectGetType:
* @conn: pointer to the hypervisor connection * @conn: pointer to the hypervisor connection
* *
* Get the name of the Hypervisor software used. * Get the name of the Hypervisor driver used. This is merely the driver
* name; for example, both KVM and QEMU guests are serviced by the
* driver for the qemu:// URI, so a return of "QEMU" does not indicate
* whether KVM acceleration is present. For more details about the
* hypervisor, use virConnectGetCapabilities().
* *
* Returns NULL in case of error, a static zero terminated string otherwise. * Returns NULL in case of error, a static zero terminated string otherwise.
* *
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册