From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH qemu-server, manager v5 0/4] fix #1926 autodetect xtermjs or novnc for VM console
Date: Tue, 8 Apr 2025 12:38:21 +0200 [thread overview]
Message-ID: <6d5bca9a-47c9-4de1-805c-af635374b261@proxmox.com> (raw)
In-Reply-To: <20250407162718.495812-1-a.lauterer@proxmox.com>
sent a v6
https://lore.proxmox.com/pve-devel/20250408103715.1081055-1-a.lauterer@proxmox.com/
On 2025-04-07 18:27, Aaron Lauterer wrote:
> This version 5 of the series uses a different approach as discussed [0] in
> the last interation.
> We add a new property in the VM status/current API result that includes
> the display configurtion of the VM. This way we can check in the
> frontend what to do with it.
>
> I chose a nested return value, as that makes it easier to add/move
> additional display properties into it.
>
> The first patch just adds the serial property to the API docs as it was
> missing. So not really related to this series, but I came across it.
>
>
> Patch 2/4 adds the new display property. If not explicitly set in the VM
> config, it will return the default 'std' value.
>
> Patch 3/4 implements the changes in the UI. The final result isn't
> really a lot simpler on the UI side than in V4 where we had the extra
> API call to the VM's config directly. Because we still need to wait for
> the API call to finish when initially navigating to the VM. But we have
> one fewer call.
>
> Patch 4/4 then introduces some changes to make loading of the console
> faster if we just navigate in the submenu of a VM itself where we
> already have the current status of a VM already cached.
>
> [0] https://lore.proxmox.com/pve-devel/49bcd58f-aba2-4c1e-a6a0-d21828a335bf@proxmox.com/
>
> qemu-server: Aaron Lauterer (2):
> vmstatus_return_properties: add missing serial property
> api: status/current: add display property
>
> PVE/API2/Qemu.pm | 13 +++++++++++++
> PVE/QemuServer.pm | 5 +++++
> 2 files changed, 18 insertions(+)
>
>
> manager: Aaron Lauterer (2):
> fix #1926 ui: vm console: autodetect novnc or xtermjs
> ui: console: check on activate if display info for VMs is present
>
> www/manager6/VNCConsole.js | 60 ++++++++++++++++++++++++++-----------
> www/manager6/qemu/Config.js | 8 ++++-
> 2 files changed, 50 insertions(+), 18 deletions(-)
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-08 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 16:27 Aaron Lauterer
2025-04-07 16:27 ` [pve-devel] [PATCH qemu-server v5 1/4] vmstatus_return_properties: add missing serial property Aaron Lauterer
2025-04-07 19:56 ` [pve-devel] applied: " Thomas Lamprecht
2025-04-07 16:27 ` [pve-devel] [PATCH qemu-server v5 2/4] api: status/current: add display property Aaron Lauterer
2025-04-07 19:58 ` Thomas Lamprecht
2025-04-08 7:49 ` Fiona Ebner
2025-04-08 9:10 ` Aaron Lauterer
2025-04-07 16:27 ` [pve-devel] [PATCH manager v5 3/4] fix #1926 ui: vm console: autodetect novnc or xtermjs Aaron Lauterer
2025-04-08 8:08 ` Dominik Csapak
2025-04-07 16:27 ` [pve-devel] [PATCH manager v5 4/4] ui: console: check on activate if display info for VMs is present Aaron Lauterer
2025-04-08 8:10 ` Dominik Csapak
2025-04-08 9:51 ` Aaron Lauterer
2025-04-08 10:38 ` Aaron Lauterer [this message]
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=6d5bca9a-47c9-4de1-805c-af635374b261@proxmox.com \
--to=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal