/openbmc/qemu/ui/ |
H A D | dbus.h | 417a2319 Wed Feb 16 12:52:14 CST 2022 Marc-André Lureau <marcandre.lureau@redhat.com> ui/dbus: associate the DBusDisplayConsole listener with the given console
DBusDisplayConsole is specific to a given QemuConsole.
Fixes: commit 142ca628 ("ui: add a D-Bus display backend") Reported-by: Akihiko Odaki <akihiko.odaki@gmail.com> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com> 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | dbus-console.c | 417a2319 Wed Feb 16 12:52:14 CST 2022 Marc-André Lureau <marcandre.lureau@redhat.com> ui/dbus: associate the DBusDisplayConsole listener with the given console
DBusDisplayConsole is specific to a given QemuConsole.
Fixes: commit 142ca628 ("ui: add a D-Bus display backend") Reported-by: Akihiko Odaki <akihiko.odaki@gmail.com> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com> 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | dbus.c | 417a2319 Wed Feb 16 12:52:14 CST 2022 Marc-André Lureau <marcandre.lureau@redhat.com> ui/dbus: associate the DBusDisplayConsole listener with the given console
DBusDisplayConsole is specific to a given QemuConsole.
Fixes: commit 142ca628 ("ui: add a D-Bus display backend") Reported-by: Akihiko Odaki <akihiko.odaki@gmail.com> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com> 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | dbus-error.c | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | dbus-display1.xml | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | dbus-listener.c | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | meson.build | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | trace-events | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
/openbmc/qemu/include/qemu/ |
H A D | dbus.h | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
/openbmc/qemu/scripts/ |
H A D | meson-buildoptions.sh | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
/openbmc/qemu/qapi/ |
H A D | ui.json | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
/openbmc/qemu/ |
H A D | meson_options.txt | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | meson.build | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|
H A D | qemu-options.hx | 142ca628 Thu Jul 15 02:53:53 CDT 2021 Marc-André Lureau <marcandre.lureau@redhat.com> ui: add a D-Bus display backend
The "dbus" display backend exports the QEMU consoles and other UI-related interfaces over D-Bus.
By default, the connection is established on the session bus, but you can specify a different bus with the "addr" option.
The backend takes the "org.qemu" service name, while still allowing further instances to queue on the same name (so you can lookup all the available instances too). It accepts any number of clients at this point, although this is expected to evolve with options to restrict clients, or only accept p2p via fd passing.
The interface is intentionally very close to the internal QEMU API, and can be introspected or interacted with busctl/dfeet etc:
$ ./qemu-system-x86_64 -name MyVM -display dbus $ busctl --user introspect org.qemu /org/qemu/Display1/Console_0
org.qemu.Display1.Console interface - - - .RegisterListener method h - - .SetUIInfo method qqiiuu - - .DeviceAddress property s "pci/0000/01.0" emits-change .Head property u 0 emits-change .Height property u 480 emits-change .Label property s "VGA" emits-change .Type property s "Graphic" emits-change .Width property u 640 emits-change [...]
See the interfaces XML source file and Sphinx docs for the generated API documentations.
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com>
|