summaryrefslogtreecommitdiffstats
path: root/include
diff options
context:
space:
mode:
authorMarc-André Lureau2019-02-21 12:07:03 +0100
committerGerd Hoffmann2019-02-22 07:42:59 +0100
commitd8aec9d9f129e6879ae0669623981892deff86f2 (patch)
tree0c8e70bbb9eae59cc1503773965fd8ad5ee9062b /include
parentspice: use a default name for the server (diff)
downloadqemu-d8aec9d9f129e6879ae0669623981892deff86f2.tar.gz
qemu-d8aec9d9f129e6879ae0669623981892deff86f2.tar.xz
qemu-d8aec9d9f129e6879ae0669623981892deff86f2.zip
display: add -display spice-app launching a Spice client
Add a new display backend that will configure Spice to allow a remote client to control QEMU in a similar fashion as other QEMU display backend/UI like GTK. For this to work, it will set up Spice server with a unix socket, and register a VC chardev that will be exposed as Spice ports. A QMP monitor is also exposed as a Spice port, this allows the remote client fuller qemu control and state handling. - doesn't handle VC set_echo() - this doesn't seem a strong requirement, very few front-end use it - spice options can be tweaked with other -spice arguments - Windows support shouldn't be hard to do, but will probably use a TCP port instead - we may want to watch the child process to quit automatically if it crashed Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Tested-by: Victor Toso <victortoso@redhat.com> Message-id: 20190221110703.5775-12-marcandre.lureau@redhat.com [ kraxel: squash incremental fix ] Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions