3a453266e3
Add a standalone VNC server binary that connects to a running QEMU instance via the D-Bus display interface (org.qemu.Display1, via the bus or directly p2p). This allows serving a VNC display without compiling VNC support directly into the QEMU system emulator, and enables running the VNC server as a separate process with independent lifecycle and privilege domain. Built only when both VNC and D-Bus display support are enabled. If we wanted to have qemu -vnc disabled, and qemu-vnc built, we would need to split CONFIG_VNC. This is left as a future exercise. Current omissions include some QEMU VNC runtime features (better handled via restart), legacy options, and Windows support. Reviewed-by: Daniel P. Berrangé <berrange@redhat.com> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
34 lines
862 B
ReStructuredText
34 lines
862 B
ReStructuredText
.. _dbus-display:
|
|
|
|
D-Bus display
|
|
=============
|
|
|
|
QEMU can export the VM display through D-Bus (when started with ``-display
|
|
dbus``), to allow out-of-process UIs, remote protocol servers or other
|
|
interactive display usages.
|
|
|
|
Various specialized D-Bus interfaces are available on different object paths
|
|
under ``/org/qemu/Display1/``, depending on the VM configuration.
|
|
|
|
QEMU also implements the standard interfaces, such as
|
|
`org.freedesktop.DBus.Introspectable
|
|
<https://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces>`_.
|
|
|
|
.. contents::
|
|
:local:
|
|
:depth: 1
|
|
|
|
.. only:: sphinx4
|
|
|
|
.. dbus-doc:: ui/dbus-display1.xml
|
|
|
|
.. only:: not sphinx4
|
|
|
|
.. warning::
|
|
Sphinx 4 is required to build D-Bus documentation.
|
|
|
|
This is the content of ``ui/dbus-display1.xml``:
|
|
|
|
.. literalinclude:: ../../ui/dbus-display1.xml
|
|
:language: xml
|