From: Dominik Csapak <d.csapak@proxmox.com>
To: Kaiyang Wu <wukaiyang2003@gmail.com>, pve-devel@lists.proxmox.com
Cc: Kaiyang Wu <wukaiyang@loongfans.cn>
Subject: Re: [PATCH qemu-server v3 0/2] qemuserver: fix virtio-gpu not being available on aarch64
Date: Thu, 16 Jul 2026 16:13:38 +0200 [thread overview]
Message-ID: <8f16c24a-bc04-40b9-880e-0a2f0d49c7db@proxmox.com> (raw)
In-Reply-To: <20260716104440.302873-1-wukaiyang@loongfans.cn>
thanks, patches look good to me now
Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
Tested-by: Dominik Csapak <d.csapak@proxmox.com>
On 7/16/26 12:44 PM, Kaiyang Wu wrote:
> Replace 'virtio-vga-gl' with 'virtio-gpu-gl' to use the correct variant of
> virtio-gpu on aarch64, and fix the detection of libGL and libEGL libraries on
> non-x86_64 architectures.
>
> Changes v2 -> v3:
> - Use 'map_vga_model' subroutine to map VGA models to device names on different
> architectures accordingly (as suggested by Dominik Csapak
> <d.csapak@proxmox.com>)
>
> Changes v1 -> v2:
> - Use the host architecture to locate the libraries (as suggested by Dominik
> Csapak <d.csapak@proxmox.com>)
> - Replace 'virtio-vga-gl' with 'virtio-gpu-gl' on aarch64 to make virtio-gl
> display option available on aarch64
>
> Kaiyang Wu (2):
> qemuserver: make base path of libGL and libEGL libraries
> architecture-aware
> qemuserver: make vga model mapping architecture-aware
>
> src/PVE/QemuServer.pm | 34 ++++++++++++++++++++++------------
> 1 file changed, 22 insertions(+), 12 deletions(-)
>
prev parent reply other threads:[~2026-07-16 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 10:43 [PATCH qemu-server v3 0/2] qemuserver: fix virtio-gpu not being available on aarch64 Kaiyang Wu
2026-07-16 10:43 ` [PATCH qemu-server v3 1/2] qemuserver: make base path of libGL and libEGL libraries architecture-aware Kaiyang Wu
2026-07-16 10:43 ` [PATCH qemu-server v3 2/2] qemuserver: make vga model mapping architecture-aware Kaiyang Wu
2026-07-16 14:13 ` Dominik Csapak [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=8f16c24a-bc04-40b9-880e-0a2f0d49c7db@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=wukaiyang2003@gmail.com \
--cc=wukaiyang@loongfans.cn \
/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.