From: Marc-André Lureau <[email protected]> The -chardev vc documentation only mentioned the built-in console with optional size parameters, but the actual behavior depends on the display backend. Document the GTK (libvte), D-Bus and spice-app cases.
Reviewed-by: Daniel P. Berrangé <[email protected]> Signed-off-by: Marc-André Lureau <[email protected]> --- qemu-options.hx | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/qemu-options.hx b/qemu-options.hx index 5566da41a36..e7842b10c8c 100644 --- a/qemu-options.hx +++ b/qemu-options.hx @@ -4286,8 +4286,17 @@ The available backends are: and hub devices is not supported as well. ``-chardev vc,id=id[[,width=width][,height=height]][[,cols=cols][,rows=rows]]`` - Connect to a QEMU text console. ``vc`` may optionally be given a - specific size. + Connect to a QEMU text console. The implementation and supported feature + set depend on the selected display backend. + + - The GTK backend uses libvte for the emulation and display (when available). + + - The D-Bus backend exports the character device as a Chardev object. + + - spice-app backend exports it as a Spice port. + + In other cases, QEMU uses its own emulated VT100, and ``vc`` may optionally be + given a specific size. ``width`` and ``height`` specify the width and height respectively of the console, in pixels. -- 2.54.0
