Skip to content
  • Daniel P. Berrangé's avatar
    7b5fa0b5
    ui: add support for remote power control to VNC server · 7b5fa0b5
    Daniel P. Berrangé authored
    
    
    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: default avatarDaniel P. Berrangé <berrange@redhat.com>
    
    [ kraxel: rebase to master  ]
    [ kraxel: add missing break ]
    
    Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
    7b5fa0b5
    ui: add support for remote power control to VNC server
    Daniel P. Berrangé authored
    
    
    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: default avatarDaniel P. Berrangé <berrange@redhat.com>
    
    [ kraxel: rebase to master  ]
    [ kraxel: add missing break ]
    
    Signed-off-by: default avatarGerd Hoffmann <kraxel@redhat.com>
Loading