Search results

  1. J

    VirGL hardware accelerated h264/h265

    I was hoping to scroll to the bottom of this and find it all working :( was hoping i could give one to my docker VM and then pass that to some docker containers for hardware accelerated stuff. https://gitlab.com/qemu-project/qemu/-/issues/2196
  2. J

    How fast is your backup datastore? Benchmark tool

    Uploaded 171 chunks in 5 seconds. Time per request: 29563 microseconds. TLS speed: 141.88 MB/s SHA256 speed: 332.99 MB/s Compression speed: 355.48 MB/s Decompress speed: 493.69 MB/s AES256/GCM speed: 185.94 MB/s Verify speed: 197.33 MB/s ┌───────────────────────────────────┬───────────────────┐...
  3. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    Just doing some more testing. Seems to be good for 4k h264 8-bit, 4k h265 10bit Proxmox host on kernel 5.16.20-edge lxc ubuntu 22.04 jellyfin-server_10.8.3-1_amd64.deb jellyfin-web_10.8.3-1_all.deb jellyfin_10.8.3-1_all.deb jellyfin-ffmpeg5_5.0.1-8 ppa:kisak/kisak-mesa which gives you VA-API...
  4. J

    [update] Wake (and other) on LAN for VMs (v0.3)

    Thank you, still works on 7.X Only had to change the file called to before systemctl would allow me to enable it.
  5. J

    cset failing (PVE7)

    So it only seems to work for processes started after the command has been run? Tho these posts seems to make me think thats not the case (tho they appear to be running bare kvm/qemu) https://www.reddit.com/r/VFIO/comments/j1a5jm/cpu_pinning_explaination/...
  6. J

    cset failing (PVE7)

    Did you get this working? Was about to start using isolcpus but stumbled across cset, but found it doesn't work on 7.x If your able to post your example, that would greatly help.
  7. J

    Changes to FSTAB mounting, now uses systemd?

    Am i showing my age then, using fstab :teehee:
  8. J

    Changes to FSTAB mounting, now uses systemd?

    so i had a nice fstab which depended on a few things being mounted before the next. I'm using mergerfs and then using bind to make the location a bit easyier to remember. After a new install of proxmox 7 it seems that everything is being mounted at once, which can then cause an issue with my...
  9. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    Tested last night with a RX560 and then Ryzen 5 5700G on POP_OS 21.10 installed Kodi (19.1 was in the pop repo) and both worked fine showing hw decode h265 10bit HDR content and playing it back on a 1080 display. Tho the 5700G got very sutterey/jumpy (didn't say it was dropping of skipping...
  10. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    Just done updates to the container no change, still get this error with hardware HDR 10-bit enabled [Parsed_tonemap_vaapi_1 @ 0x557553e70640] VAAPI driver doesn't support HDR [Parsed_tonemap_vaapi_1 @ 0x557553e70640] Failed to configure output pad on Parsed_tonemap_vaapi_1 If i disable "VPP...
  11. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    You gave me the idea to try the beta/bleeding edge drivers. with HEVC Main 10 60fps i have to allow the container 15 threads through to get it to transcode to 1080 10Mbps, and even then it can out play the transcode buffer. Hopefully it will just get better from here as mesa gets updated.
  12. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    These are the few extras i installed on the host for Ryzen https://github.com/Ta180m/zenpower3 https://hattedsquirrel.net/2021/02/ryzen-cpu-performance-monitor-tool-for-linux/ https://gitlab.com/leogx9r/ryzen_smu
  13. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    Thats correct. Just that PPA on the lxc container, nothing more than microcode on the host https://wiki.debian.org/Microcode#Debian_11_.22Bullseye.22_.28stable.29 # CPU Microcode deb http://deb.debian.org/debian bullseye main contrib non-free deb http://security.debian.org/debian-security...
  14. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    Fresh install of proxmox, all updates and amd-microcode installed. Fresh container of ubuntu 20.04 (from the normal proxmox container location) Installed the latest stable jellyfin using the normal ubuntu guide they have. installed these mesa drivers, from testing...
  15. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    Sorry, I've not been anywhere near clear with my posts, due to only having a few hours in the evenings to test (stealing my wife's monitor and keyboard) First i tried a lxc container in proxmox, then on the proxmox host its self. New install of Ubuntu 21.10 on bare metal and install jellyfin...
  16. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    I've tried the Ubuntu and Debian stable packages. Lxc. So the crashs seems to randomly happen, there is a HDR 10bit file I can get it to always crash on, but it also randomly happens to h264 and h265.
  17. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    So it worked without crashing yesterday with my testing. Started testing today, and after 3 tests i got the [ 4297.709401] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring vcn_enc0 timeout, signaled seq=6, emitted seq=7 [ 4297.710112] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process...
  18. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    So i changed back to jellyfin ffmpeg, and it's now working ! (tho only on my test desktop Ubuntu....) This is crazy.
  19. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    tried /usr/lib/jellyfin-ffmpeg/ffmpeg ffmpeg version 4.4.1-Jellyfin Copyright (c) 2000-2021 the FFmpeg developers built with gcc 11 (Ubuntu 11.2.0-7ubuntu2) Causes the kernel error and /usr/bin/ffmpeg ffmpeg version 4.4-6ubuntu5 Copyright (c) 2000-2021 the FFmpeg developers built with gcc 11...
  20. J

    proxmox 7.1, unable to access render128 in lxc with vainfo

    That's a good point, think I got to focused on jellyfin. Just installed normal Ubuntu, same errors. I'll try again tomorrow with something else (or different ffmpeg) Just tried the same files with MPV with -hwdec no crash. Now really time to stop

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!