aboutsummaryrefslogtreecommitdiff
path: root/ui/vnc-enc-zlib.c
diff options
context:
space:
mode:
authorLaurent Vivier <laurent@vivier.eu>2019-09-06 10:38:12 +0200
committerGerd Hoffmann <kraxel@redhat.com>2019-09-17 13:43:22 +0200
commit6105683da35babad9ae168a72d1e89e63e9d6974 (patch)
tree46faa844b75b726401f64c0ff52b2532ff122921 /ui/vnc-enc-zlib.c
parente1b3d47751a420835cb0560fd029c39fea961a79 (diff)
downloadqemu-6105683da35babad9ae168a72d1e89e63e9d6974.zip
qemu-6105683da35babad9ae168a72d1e89e63e9d6974.tar.gz
qemu-6105683da35babad9ae168a72d1e89e63e9d6974.tar.bz2
ui: add an embedded Barrier client
This allows to receive mouse and keyboard events from a Barrier server. This is enabled by adding the following parameter on the command line ... -object input-barrier,id=$id,name=$name ... Where $name is the name declared in the screens section of barrier.conf The barrier server (barriers) must be configured and must run on the local host. For instance: section: screens localhost: ... VM-1: ... end section: links localhost: right = VM-1 VM-1: left = localhost end Then on the QEMU command line: ... -object input-barrier,id=barrie0,name=VM-1 ... When the mouse will move out of the screen of the local host on the right, the mouse and the keyboard will be grabbed and all related events will be send to the guest OS. This is usefull when qemu is configured without emulated graphic card but with a VFIO attached graphic card. More information about Barrier can be found at: https://github.com/debauchee/barrier This avoids to install the Barrier server in the guest OS, for instance when it is not supported or during the installation. Signed-off-by: Laurent Vivier <laurent@vivier.eu> Message-id: 20190906083812.29487-1-laurent@vivier.eu Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'ui/vnc-enc-zlib.c')
0 files changed, 0 insertions, 0 deletions