From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Roque Arcudia Hernandez <roqueh@google.com>
Cc: ankeesler@google.com, mst@redhat.com,
marcandre.lureau@redhat.com, qemu-devel@nongnu.org,
venture@google.com
Subject: Re: [PATCH 1/2] ui: Allow injection of vnc display name
Date: Tue, 22 Oct 2024 08:14:29 +0100 [thread overview]
Message-ID: <ZxdQ1XPZSC6U7fHU@redhat.com> (raw)
In-Reply-To: <20241017215304.3916866-2-roqueh@google.com>
On Thu, Oct 17, 2024 at 09:53:03PM +0000, Roque Arcudia Hernandez wrote:
> From: Andrew Keesler <ankeesler@google.com>
>
> Thanks to 72d277a7, 1ed2cb32, and others, EDID (Extended Display Identification
> Data) is propagated by QEMU such that a virtual display presents legitimate
> metadata (e.g., name, serial number, preferred resolutions, etc.) to its
> connected guest.
>
> This change propagates an optional user-provided display name to
> QemuConsole. Future changes will update downstream devices to leverage this
> display name for various uses, the primary one being providing a custom EDID
> name to guests. Future changes will also update other displays (e.g., spice)
> with a similar option to propagate a display name to downstream devices.
>
> Currently, every virtio-gpu virtual display has the same name: "QEMU
> Monitor". We hope to be able to inject the EDID name of virtual displays in
> order to test guest behavior that is specific to display names. We provide the
> ability to inject the display name from the display configuration as that most
> closely resembles how real displays work (hardware displays contain static EDID
> information that is provided to every connected host).
>
> It should also be noted that EDID names longer than 12 bytes will be truncated
> per spec (I think?).
>
> Signed-off-by: Andrew Keesler <ankeesler@google.com>
> Signed-off-by: Roque Arcudia Hernandez <roqueh@google.com>
> ---
> include/ui/console.h | 1 +
> ui/console-priv.h | 1 +
> ui/console.c | 8 ++++++++
> ui/vnc.c | 8 +++++++-
> 4 files changed, 17 insertions(+), 1 deletion(-)
> diff --git a/ui/vnc.c b/ui/vnc.c
> index 93a8dbd253..7d6acc5c2e 100644
> --- a/ui/vnc.c
> +++ b/ui/vnc.c
> @@ -3595,6 +3595,9 @@ static QemuOptsList qemu_vnc_opts = {
> },{
> .name = "power-control",
> .type = QEMU_OPT_BOOL,
> + },{
> + .name = "name",
> + .type = QEMU_OPT_STRING,
> },
> { /* end of list */ }
> },
> @@ -4016,7 +4019,7 @@ void vnc_display_open(const char *id, Error **errp)
> QemuOpts *opts = qemu_opts_find(&qemu_vnc_opts, id);
> g_autoptr(SocketAddressList) saddr_list = NULL;
> g_autoptr(SocketAddressList) wsaddr_list = NULL;
> - const char *share, *device_id;
> + const char *share, *device_id, *name;
> QemuConsole *con;
> bool password = false;
> bool reverse = false;
> @@ -4217,6 +4220,9 @@ void vnc_display_open(const char *id, Error **errp)
> }
> qkbd_state_set_delay(vd->kbd, key_delay_ms);
>
> + name = qemu_opt_get(opts, "name");
> + qemu_console_set_name(vd->dcl.con, name);
> +
> if (saddr_list == NULL) {
> return;
> }
The VNC protocol has a display name field that is sent to the client,
and which they would typically display in the Window titlebar. As a
user, I would expect this 'name' setting to be controlling that. It
is currently set in the 'protocol_client_init' method.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-10-22 7:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 21:53 [PATCH 0/2] Allow injection of virtio-gpu EDID name Roque Arcudia Hernandez
2024-10-17 21:53 ` [PATCH 1/2] ui: Allow injection of vnc display name Roque Arcudia Hernandez
2024-10-21 11:14 ` Marc-André Lureau
2024-10-21 20:03 ` Andrew Keesler
2024-10-22 7:49 ` Marc-André Lureau
2024-10-22 7:55 ` Daniel P. Berrangé
2024-10-22 7:53 ` Daniel P. Berrangé
2024-10-22 8:04 ` Marc-André Lureau
2024-10-22 8:10 ` Daniel P. Berrangé
2024-10-22 8:36 ` Marc-André Lureau
2024-10-28 19:25 ` Andrew Keesler
2024-11-22 14:40 ` Andrew Keesler
2024-10-22 7:14 ` Daniel P. Berrangé [this message]
2024-10-17 21:53 ` [PATCH 2/2] hw/display: Allow injection of virtio-gpu EDID name Roque Arcudia Hernandez
2024-11-25 12:04 ` Daniel P. Berrangé
2024-11-25 20:54 ` Andrew Keesler
2024-11-26 16:03 ` Daniel P. Berrangé
2024-11-26 21:07 ` Andrew Keesler
2024-12-02 20:31 ` Andrew Keesler
2024-12-05 16:59 ` Daniel P. Berrangé
2024-12-10 9:27 ` Markus Armbruster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxdQ1XPZSC6U7fHU@redhat.com \
--to=berrange@redhat.com \
--cc=ankeesler@google.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roqueh@google.com \
--cc=venture@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.