On 12/20/18 8:15 AM, Marc-André Lureau wrote:
Signed-off-by: Marc-André Lureau <marcandre.lur...@redhat.com>
---
qapi/ui.json | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/qapi/ui.json b/qapi/ui.json
index 5ad13248d5..3f2f662dca 100644
--- a/qapi/ui.json
+++ b/qapi/ui.json
@@ -1075,6 +1075,30 @@
#
# Display (user interface) type.
#
+# @default: The default user interface.
Any more hints on how this default is determined? Is it a compile-time
decision, based on what libraries were linked in? Does the work on
adding #if support to qapi make it introspectible what the default is?
+#
+# @none: No user interface or video output display. The guest will
+# still see an emulated graphics card, but its output will not
+# be displayed to the QEMU user.
+#
+# @gtk: The GTK user interface.
+#
+# @sdl: The SDL user interface.
+#
+# @egl-headless: No user interface, offload GL operations to a local
+# DRI device. Graphical display need to be paired with
+# VNC or Spice. (Since 3.1)
s/need/needs/
+#
+# @curses: Display video output via curses. For graphics device
+# models which support a text mode, QEMU can display this
+# output using a curses/ncurses interface. Nothing is
+# displayed when the graphics device is in graphical mode or
+# if the graphics device does not support a text
+# mode. Generally only the VGA device models support text
+# mode.
+#
+# @cocoa: The Cocoa user interface.
+#
# Since: 2.12
#
##
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
