public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Aaron Lauterer <a.lauterer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH qemu-server, manager v6 0/4] fix #1926 autodetect xtermjs or novnc for VM console
Date: Tue, 8 Apr 2025 14:29:09 +0200	[thread overview]
Message-ID: <7cafdc9c-ad63-4d67-9b2d-994087e5c12d@proxmox.com> (raw)
In-Reply-To: <20250408103715.1081055-1-a.lauterer@proxmox.com>

sent a v7 
https://lore.proxmox.com/pve-devel/20250408122710.1164112-2-a.lauterer@proxmox.com/T/#m54aae8f7595a1478748c2b61180c46d0cf52e38b

On  2025-04-08  12:37, Aaron Lauterer wrote:
> 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.
> 
> Patch 1/4 makes two functions in QemuServer.pm public.
> 
> 
> 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.
> 
> Changes from v5: implement suggestions:
> 
> * use get_vga_properties for default VGA
> * UI: use helper to determine if serial display
> 
> qemu-server: Aaron Lauterer (2):
>    QemuServer: make get_vga_properties and extract_version public
>    api: status/current: add display property
> 
>   PVE/API2/Qemu.pm  | 21 +++++++++++++++++++++
>   PVE/QemuServer.pm |  4 ++--
>   2 files changed, 23 insertions(+), 2 deletions(-)
> 
> 
> 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/Utils.js       |  4 +++
>   www/manager6/VNCConsole.js  | 60 ++++++++++++++++++++++++++-----------
>   www/manager6/qemu/Config.js |  7 ++++-
>   3 files changed, 53 insertions(+), 18 deletions(-)
> 
> 



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


      parent reply	other threads:[~2025-04-08 12:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 10:37 Aaron Lauterer
2025-04-08 10:37 ` [pve-devel] [PATCH qemu-server v6 1/4] QemuServer: make get_vga_properties and extract_version public Aaron Lauterer
2025-04-08 11:26   ` Fiona Ebner
2025-04-08 10:37 ` [pve-devel] [PATCH qemu-server v6 2/4] api: status/current: add display property Aaron Lauterer
2025-04-08 11:26   ` Fiona Ebner
2025-04-08 10:37 ` [pve-devel] [PATCH manager v6 3/4] fix #1926 ui: vm console: autodetect novnc or xtermjs Aaron Lauterer
2025-04-08 10:37 ` [pve-devel] [PATCH manager v6 4/4] ui: console: check on activate if display info for VMs is present Aaron Lauterer
2025-04-08 12:29 ` 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=7cafdc9c-ad63-4d67-9b2d-994087e5c12d@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