docs: add misc/qemu-backends.txt

Document the interface between qemu and libxl regarding backends
supported by qemu.

Signed-off-by: Juergen Gross <jgross@suse.com>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Reviewed-by: Wei Liu <wei.liu2@citrix.com>
Release-acked-by: Wei Liu <wei.liu2@citrix.com>
This commit is contained in:
Juergen Gross authored and Wei Liu committed 2016-04-20 18:59:11 +01:00
1 parent 8b17648339
commit 1e9f929b78
1 file changed
+21
+21
View File
@@ -0,0 +1,21 @@
In order to know whether qemu supports a specific backend type libxl
needs a way to obtain this information.
As each qemu instance owns a path (named $QEMU from now on) in
Xenstore, the backend information is presented there. $QEMU is built
from the domain id where the qemu instance is running $BACKEND_DOM,
and the domain id of the target domain of the qemu process $DOMID:
$QEMU = /local/domain/$BACKEND_DOM/device-model/$DOMID
Before signalling qemu is running by writing "running" to $QEMU/state
qemu will create a Xenstore node for each supported backend under
$QEMU/backends with the backend type as name (e.g. $QEMU/backends/qdisk
for the qdisk backend). In case qemu is running de-privileged (not as
user root) the backend nodes must be written before qemu is dropping
privileges.
libxl can assume a backend of a specific type $TYPE is supported if:
- $QEMU/backends/$TYPE is existing in Xenstore
- or $QEMU/backends is not existing and $TYPE is one of:
"console", "vkbd", "vfb", "qdisk", "qnic"
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.