aboutsummaryrefslogtreecommitdiff
path: root/util
diff options
context:
space:
mode:
authorDaniel P. Berrangé <berrange@redhat.com>2020-12-11 16:08:25 +0000
committerGerd Hoffmann <kraxel@redhat.com>2021-01-15 11:22:42 +0100
commit7b5fa0b583c8d54f4bc3be796c4086de39ea09d3 (patch)
tree798384dccac4e0086a0869bee71bf0a4e959ebb1 /util
parent521534df57cc0bee7b0da9e69fbbaa7149036ddb (diff)
downloadqemu-7b5fa0b583c8d54f4bc3be796c4086de39ea09d3.zip
qemu-7b5fa0b583c8d54f4bc3be796c4086de39ea09d3.tar.gz
qemu-7b5fa0b583c8d54f4bc3be796c4086de39ea09d3.tar.bz2
ui: add support for remote power control to VNC server
The "XVP" (Xen VNC Proxy) extension defines a mechanism for a VNC client to issue power control requests to trigger graceful shutdown, reboot, or hard reset. This option is not enabled by default, since we cannot assume that users with VNC access implicitly have administrator access to the guest OS. Thus is it enabled with a boolean "power-control" option e.g. -vnc :1,power-control=on While, QEMU can easily support shutdown and reset, there's no easy way to wire up reboot support at this time. In theory it could be done by issuing a shutdown, followed by a reset, but there's no convenient wiring for such a pairing in QEMU. It also isn't possible to have the VNC server directly talk to QEMU guest agent, since the agent chardev is typically owned by an external mgmt app. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> [ kraxel: rebase to master ] [ kraxel: add missing break ] Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'util')
0 files changed, 0 insertions, 0 deletions