Search results

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

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...

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

with our mesa on the host i still get the same crash. Ubuntu 20.04 vainfo: VA-API version: 1.7 (libva 2.6.0) vainfo: Driver version: Mesa Gallium driver 21.0.3 for AMD RENOIR (DRM 3.41.0, 5.13.19-2-pve, LLVM 12.0.0) vainfo: Supported profile and entrypoints Ubunti 21.10 vainfo: VA-API version...

just tested locking the GPU to 1000Mhz in the BIOS (Asus motherboard), same crash. Was along shot that the changing of powerstate/speed was causing an issue. Blown away the host and will try a container with mesa and host with no mesa.

I tried Ubuntu 18.04 and 21.04 but I couldn't get them to see the hardware (I think cause the mesa was different between host and the container)

So I'm using a plain debain container and then installing jellyfin. I get the same errors if I run jellyfin on the host. I'm just using the mesa-va drivers, might try the proper amd drivers.

Under clocked and disable DOCP (or what erver AMD call XMP profiles) Same crash issues on host. Found someone talking bout amdgpu.dpm=0 but this then fails to boot. https://www.reddit.com/r/jellyfin/comments/ovvo7o/transcoding_on_amd_4650g_not_working/

Seems to happen on the host as well now, but not always, it happens always on the container.

Got a little further, seems jellyfin guide had an update to include proxmox. https://jellyfin.org/docs/general/administration/hardware-acceleration.html#lxc-container-on-proxmox Now getting what i think are DRM or power issues. [4287.669230] amdgpu 0000:07:00.0: amdgpu: [mmhub0] retry page...

So i've followed guides https://forum.proxmox.com/threads/amd-ryzen-7-renoir-4750g-apu-and-igpu-pass-thru-to-windows-10-guest.84849/page-3 https://emby.media/community/index.php?/topic/49680-howto-vaapi-transcoding-inside-lxc-container/ and runinng vainfo on the host shows the list of...

root@pve1:~# ethtool -i enp3s0 driver: igb version: 5.13.19-2-pve firmware-version: 0. 6-1 expansion-rom-version: bus-info: 0000:03:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes Just about to install the intel...

Brand new install of proxmox 7.1 UEFI with ZFS root on my ASUS x570 with an intel nic i211, got the same issue. If i down and then up the interface 30+ seconds after boot (from the console) it all starts working. Gonna hold off sawpping out my i5 as i have no ILO and don't wanna rely on a a...

It is a cluster (sorry should have said that) can't upgrade to 7.1 as we have containers that have an old version of systemd :(

We only have containers, i'm unsure if it happens when trying to connect to the host as well tho, will see when it next happens IP and MAC have been changed to protect the innocent arch: amd64 cmode: console cores: 2 hostname: SV1000-Test-SUSE15.2 memory: 2048 nameserver: 8.8.8.8 8.8.4.4...

So we keep getting this error on a lot of workstations when we have been logged into the host (with firefox, chrome or IE) it seems to happen randomly, but when we come back to the logged in session and click on a console for a container we get get "failed" if you look into the logs it says...

So there are a few more things we (people) need to know. What File systems are you using ? Have you tweaked the ZFS memory settings ? How are you seeing how much RAM is used ? the gui, htop, free What settings do you have on the cache for the disks in the guests ? I think thats about it but all...

I would still test as above. to VMs both attched to bmvr6 with static address, to see if they can ping each other. I'm still leaning towards the swtich not forwarding/allowing tagged/untagged packets into the right places.

To test, add another virtual with the same setup and set a static address on both virtuals, in the same address space as your normal network. Make sure they are on the same VLAN in proxmox and the same network bridge. See if they can talk/ping each other (windows blocks ping responses by...

Quick reply, have you made sure that VLAN aware on the network device of the host is ticked ? also make sure your tagging is sent on the VLAN for the virtual interface being passed to the virtual machine. Also check that your switch is not a managed one (if it is you might need to enable VLANs...