2024-08-25, 11:33 AM
(This post was last modified: 2024-08-25, 11:40 AM by designingbeing. Edited 2 times in total.)
Thanks for the reply
- My container was always privileged
- I think the drivers might have been the issue.
On Proxmox host I could see:
On the LXC guest I could see:
On the LXC guest I then ran:
and on the proxmox host, updated my LXC.conf with the value from "getent group render | cut -d":" -f3" as run on the LXC guest
then rebooted the LXC.
After this I forced a transcode and for the first time saw activity in "intel_gpu_top" as run on the Proxmox host
I'm cautiously optimistic that this has resolved the issue. Thank you for your input.
(2024-08-25, 09:48 AM)Fate Wrote: My mounts look a bit different in lxc conf:
Code:lxc.cgroup2.devices.allow: c 226:0 rwm
lxc.cgroup2.devices.allow: c 226:128 rwm
lxc.cgroup2.devices.allow: c 29:0 rwm
lxc.mount.entry: /dev/fb0 dev/fb0 none bind,optional,create=file
lxc.mount.entry: /dev/dri dev/dri none bind,optional,create=dir
lxc.mount.entry: /dev/dri/renderD128 dev/dri/renderD128 none bind,optional,create=file
Was your container always privileged? I think if you have changed from unprivileged to privileged you have to reset the user/group ids. (probably easier to reinstall the container)
I would recommend tteck scripts to create your container if you are unsure.
Which intel drivers did you install on the proxmox and on the lxc side?
- My container was always privileged
- I think the drivers might have been the issue.
On Proxmox host I could see:
Code:
i965-va-driver-shaders/stable,now 2.4.1-1 amd64 [installed]
intel-media-va-driver-non-free/stable,now 23.1.1+ds1-1 amd64 [installed]
On the LXC guest I could see:
Code:
i965-va-driver/stable,now 2.4.1+dfsg1-1 amd64 [installed,automatic]
intel-media-va-driver/stable,now 23.1.1+dfsg1-1 amd64 [installed,automatic]
On the LXC guest I then ran:
Code:
apt install software-properties-common -y
add-apt-repository -y non-free
apt install intel-media-va-driver-non-free -y
and on the proxmox host, updated my LXC.conf with the value from "getent group render | cut -d":" -f3" as run on the LXC guest
Code:
lxc.hook.pre-start: sh -c "chown 0:{LXC getent output} /dev/dri/renderD128"
then rebooted the LXC.
After this I forced a transcode and for the first time saw activity in "intel_gpu_top" as run on the Proxmox host
I'm cautiously optimistic that this has resolved the issue. Thank you for your input.