Could you give a quick summary of the steps you took?I just started the make deb portion, it's failing when it gets to the
FAILED: libcommon.a.p/hw_display_virtio-gpu-virgl.c.o . Applied the patch from pve-qemu/qemu directory with patch < virgl.patch
##edit
I started the process on another identical host, did NOT use bookworm-backports, used the deb-src for bookworm in sources.list, ran apt-get build-dep qemu virglrenderer. This installed almost everything. Builds fine after this.
Hey, let me set this up a couple more times as I take notes, then I'll post my steps. I have a correction, I do use backports, but for installing the updated mesa libs AFTER using :Could you give a quick summary of the steps you took?
I am interested in this, but do not want to mess up my proxmox too much with custom packets....
As in the tutorial above some steps were marked as maybe not necessairy.
Please, anyone following these steps, don't do this on a production machine and as mentioned, to maintain this, you have to reinstall your custom qemu every time proxmox updates.Would be very nice if you could post this in the devel list [1] or at the very least post a feature request in bugzilla [2] to get this compiled by default, as it is a nice feature and this kind of modifications will be overwritten on updates and are quite hard to maintain at scale.
Thanks!
[1] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
[2] https://bugzilla.proxmox.com/
Please, post the link to the bug report. I can't find it and would like to follow it. Thanks!I did post this in bugzilla as you requested.
I may have done it wrong, but here is the link:Please, post the link to the bug report. I can't find it and would like to follow it. Thanks!
user@debian:~$ vainfo
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/virtio_gpu_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 25.0.4-1~bpo12+1 for virgl (NVE6)
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
What does vainfo on the host show?Hi all! This is what i have after install Mesa 25:
What should i do?Bash:user@debian:~$ vainfo libva info: VA-API version 1.17.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/virtio_gpu_drv_video.so libva info: Found init function __vaDriverInit_1_17 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.17 (libva 2.12.0) vainfo: Driver version: Mesa Gallium driver 25.0.4-1~bpo12+1 for virgl (NVE6) vainfo: Supported profile and entrypoints VAProfileNone : VAEntrypointVideoProc
Understand that H264/265 codecs are NOT FREE PRODUCTS, and they require a license. see https://accessadvance.com/ for more information.@cheiss Dear Staff members, can we have virgl encode/decode like normal in Proxmox by default? Thank you!
From host1:What does vainfo on the host show?
# vainfo
error: can't connect to X server!
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 25.0.4-1~bpo12+1 for AMD FirePro S7150 (radeonsi, tonga, ACO, DRM 3.57, 6.8.12-10-pve)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileNone : VAEntrypointVideoProc
# vainfo
error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.17 (libva 2.12.0)
vainfo: Driver version: Mesa Gallium driver 25.0.4-1~bpo12+1 for NVE6
vainfo: Supported profile and entrypoints
VAProfileNone : VAEntrypointVideoProc
So Proxmox disabled codec in virgl driver?Understand that H264/265 codecs are NOT FREE PRODUCTS, and they require a license. see https://accessadvance.com/ for more information.
Not... exactly. its just not included.So Proxmox disabled codec in virgl driver?
Is that excluded by Proxmox development or QEMU project excluded it? If it is Proxmox made it excluded in its special version, can we make it being included?Not... exactly. its just not included.
root@pve-nuc11:/root# pveversion
pve-manager/8.1.3/b46aac3b42da5d15 (running kernel: 6.5.11-4-pve)
root@pve-nuc11:/root# vainfo
libva info: VA-API version 1.17.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_17
libva info: va_openDriver() returns 0
vainfo...
We use essential cookies to make this site work, and optional cookies to enhance your experience.