From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 5DBCD1FF15E for ; Mon, 10 Nov 2025 12:40:32 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 817A713855; Mon, 10 Nov 2025 12:41:02 +0100 (CET) From: Markus Frank To: pve-devel@lists.proxmox.com Date: Mon, 10 Nov 2025 12:25:26 +0100 Message-ID: <20251110114032.125526-1-m.frank@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1762774835379 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.001 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH qemu-server/pve-manager v1 0/2] add virtio-vga-gl Vulkan (venus) support X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" This option is represented by an enum in qemu-server and a comboBox in pve-manager, with values such as 'venus-512' and 'venus-1024'. This is to allow for the potential addition of another Vulkan implementation in the future. The number indicates the memory window in MiB for Venus. As I am not sure what the hostmem and blob properties actually do, I asked on the qemu-discuss mailing list: https://mail-archive.com/qemu-discuss@nongnu.org/msg09011.html QEMU documentation: www.qemu.org/docs/master/system/devices/virtio/virtio-gpu.html#virtio-gpu-virglrenderer To get an overview of the performance, see the benchmark below. supertuxkart (1.5) benchmark (default settings, vulkan, 1024x768): Host result (Granite Ridge integrated GPU): * Total frame count: 8488 * Total profiling time (ms): 38139 * Steady FPS: 92 * Mostly stable FPS: 137 * Typical FPS: 194 VM (host, 4 core, 8GiB) with venus (hostmem=8192M) result: * Total frame count: 3321 * Total profiling time (ms): 38130 * Steady FPS: 58 * Mostly stable FPS: 75 * Typical FPS: 86 This benchmark showed no significant differences in performance between the various memory window sizes for venus. qemu-server: Markus Frank (1): virtio-vga-gl: add Vulkan (venus) support src/PVE/QemuServer.pm | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) pve-manager: Markus Frank (1): ui: qemu: add Vulkan option in DisplayEdit www/manager6/qemu/DisplayEdit.js | 42 +++++++++++++++++++++++++++++++- 1 file changed, 41 insertions(+), 1 deletion(-) -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel