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/[email protected]/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 [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
