HW acceleration in LXC on proxmox

[LeidenSpain 33]

Hi,

 

I am another one who has installed an LXC virtual machine in proxmox but has problems with hardware acceleration:  https://github.com/tteck/Proxmox 

I have searched a lot of information for both proxmox and emby, but I can't solve it.
I am also investigating for proxmox to see where the problem is.

It happens to me, as other users have already commented, that it does not show me the graph to use it in the acceleration

 

I use an I5-10500T with UHD Graphics 630.

In the log I have detected this error message: 

{"ApplicationVersion":"4.7.8.0","VersionType":"Release","ReleaseCode":"c36cff66fb104cddb5b71f07fa6ec84d","Environment":{"OperatingSystem":"Linux","OperatingSystemName":"Unix","OperatingSystemVersion":"Linux version 5.19.7-2-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC PVE","FrameworkVersion":".NET 6.0.8","OsArchitecture":"x64","ProcessArchitecture":"x64","PathSeparator":":","IsWindowsService":false},"VideoDecoders":{},"VideoEncoders":{"1: x264 Software Encoder":{"SupportedPresets":["superfast","veryfast","faster","fast","medium","slow","slower","veryslow"],"MinConstantRateFactor":0,"MaxConstantRateFactor":51,"FrameworkCodec":"libx264","IsHardwareCodec":false,"SupportsParameters":true,"CompatibleDecoderFrameworks":[],"VideoMediaType":"h264","ProfilesWithLevel":[{"Profile":"AvcProfileBaseline","Level":"AvcLevel62"},{"Profile":"AvcProfileMain","Level":"AvcLevel62"},{"Profile":"AvcProfileHigh","Level":"AvcLevel62"},{"Profile":"AvcProfileHigh10","Level":"AvcLevel62"},{"Profile":"AvcProfileHigh422","Level":"AvcLevel62"},{"Profile":"AvcProfileHigh444","Level":"AvcLevel62"}],"SupportedProfiles":["AvcProfileBaseline","AvcProfileMain","AvcProfileHigh","AvcProfileHigh10","AvcProfileHigh422","AvcProfileHigh444"],"SupportedLevels":["AvcLevel1b","AvcLevel1","AvcLevel11","AvcLevel12","AvcLevel13","AvcLevel2","AvcLevel21","AvcLevel22","AvcLevel3","AvcLevel31","AvcLevel32","AvcLevel4","AvcLevel41","AvcLevel42","AvcLevel5","AvcLevel51","AvcLevel52","AvcLevel6","AvcLevel61","AvcLevel62"],"Direction":"Encoder","SupportedColorFormats":["yuv420p","yuvj420p","yuv422p","yuvj422p","yuv444p","yuvj444p","nv12","nv16","nv21","yuv420p10","yuv422p10","yuv444p10","nv20","gray","gray10"],"CommandGenerator":{},"CodecDeviceInfo":{"Capabilities":{"SupportsHwUpload":false,"SupportsHwDownload":false,"SupportsStandaloneDeviceInit":false,"Supports10BitProcessing":false,"SupportsNativeToneMapping":false},"Adapter":0,"Name":"Software Codec","Desription":"Software Codec","DeviceId":0,"HardwareContextFramework":"None","VendorId":0},"CodecKind":"Video","MediaTypeName":"H.264 (AVC)","MaxBitRate":"781 Mbit/s","SupportedColorFormatStrings":["YUV420P","YUVJ420P","YUV422P","YUVJ422P","YUV444P","YUVJ444P","NV12","NV16","NV21","YUV420P10","YUV422P10","YUV444P10","NV20","GRAY8","GRAY10"],"ProfileAndLevelInformation":[{"Profile":{"ShortName":"AvcProfileBaseline","Description":"Baseline Profile","Details":"Primarily for low-cost applications that require additional data loss robustness, this profile is used in some videoconferencing and mobile applications. This profile includes all features that are supported in the Constrained Baseline Profile, plus three additional features that can be used for loss robustness (or for other purposes such as low-delay multi-point video stream compositing). The importance of this profile has faded somewhat since the definition of the Constrained Baseline Profile in 2009. All Constrained Baseline Profile bitstreams are also considered to be Baseline Profile bitstreams, as these two profiles share the same profile identifier code value.","Id":"AvcProfiles.AvcProfileBaseline","BitDepths":[8]},"Level":{"ShortName":"AvcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"781 Mbit/s","MaxBitRateDisplay":"781 Mbit/s","Id":"AvcLevels.AvcLevel62","ResolutionRates":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRateStrings":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRatesDisplay":"8192x4320@120, 7680x4320@129, 3840x2160@300"}},{"Profile":{"ShortName":"AvcProfileMain","Description":"Main Profile","Details":"This profile is used for standard-definition digital TV broadcasts that use the MPEG-4 format as defined in the DVB standard. It is not, however, used for high-definition television broadcasts, as the importance of this profile faded when the High Profile was developed in 2004 for that application.","Id":"AvcProfiles.AvcProfileMain","BitDepths":[8]},"Level":{"ShortName":"AvcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"781 Mbit/s","MaxBitRateDisplay":"781 Mbit/s","Id":"AvcLevels.AvcLevel62","ResolutionRates":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRateStrings":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRatesDisplay":"8192x4320@120, 7680x4320@129, 3840x2160@300"}},{"Profile":{"ShortName":"AvcProfileHigh","Description":"High Profile","Details":"The primary profile for broadcast and disc storage applications, particularly for high-definition television applications (for example, this is the profile adopted by the Blu-ray Disc storage format and the DVB HDTV broadcast service).","Id":"AvcProfiles.AvcProfileHigh","BitDepths":[8]},"Level":{"ShortName":"AvcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"781 Mbit/s","MaxBitRateDisplay":"781 Mbit/s","Id":"AvcLevels.AvcLevel62","ResolutionRates":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRateStrings":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRatesDisplay":"8192x4320@120, 7680x4320@129, 3840x2160@300"}},{"Profile":{"ShortName":"AvcProfileHigh10","Description":"High 10 Profile","Details":"Going beyond typical mainstream consumer product capabilities, this profile builds on top of the High Profile, adding support for up to 10 bits per sample of decoded picture precision.","Id":"AvcProfiles.AvcProfileHigh10","BitDepths":[10]},"Level":{"ShortName":"AvcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"781 Mbit/s","MaxBitRateDisplay":"781 Mbit/s","Id":"AvcLevels.AvcLevel62","ResolutionRates":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRateStrings":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRatesDisplay":"8192x4320@120, 7680x4320@129, 3840x2160@300"}},{"Profile":{"ShortName":"AvcProfileHigh422","Description":"High 4:2:2 Profile","Details":"Primarily targeting professional applications that use interlaced video, this profile builds on top of the High 10 Profile, adding support for the 4:2:2 chroma subsampling format while using up to 10 bits per sample of decoded picture precision.","Id":"AvcProfiles.AvcProfileHigh422","BitDepths":[10]},"Level":{"ShortName":"AvcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"781 Mbit/s","MaxBitRateDisplay":"781 Mbit/s","Id":"AvcLevels.AvcLevel62","ResolutionRates":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRateStrings":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRatesDisplay":"8192x4320@120, 7680x4320@129, 3840x2160@300"}},{"Profile":{"ShortName":"AvcProfileHigh444","Description":"High 4:4:4 Predictive Profile","Details":"This profile builds on top of the High 4:2:2 Profile, supporting up to 4:4:4 chroma sampling, up to 14 bits per sample, and additionally supporting efficient lossless region coding and the coding of each picture as three separate color planes.","Id":"AvcProfiles.AvcProfileHigh444","BitDepths":[10,12,14]},"Level":{"ShortName":"AvcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"781 Mbit/s","MaxBitRateDisplay":"781 Mbit/s","Id":"AvcLevels.AvcLevel62","ResolutionRates":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRateStrings":["8192x4320@120","7680x4320@129","3840x2160@300"],"ResolutionRatesDisplay":"8192x4320@120, 7680x4320@129, 3840x2160@300"}}],"Id":"V-E-libx264","Name":"x264 Software Encoder","SecondaryFramework":"None","IsEnabledByDefault":false,"DefaultPriority":0},"2: x265 Software Encoder":{"SupportedPresets":["ultrafast","superfast","veryfast","faster","fast","medium","slow","slower","veryslow","placebo"],"MinConstantRateFactor":0,"MaxConstantRateFactor":51,"FrameworkCodec":"libx265","IsHardwareCodec":false,"SupportsParameters":true,"CompatibleDecoderFrameworks":[],"VideoMediaType":"hevc","ProfilesWithLevel":[{"Profile":"HevcProfileMain","Level":"HevcLevel62"},{"Profile":"HevcProfileMain10","Level":"HevcLevel62"}],"SupportedProfiles":["HevcProfileMain","HevcProfileMain10"],"SupportedLevels":["HevcLevel1","HevcLevel2","HevcLevel21","HevcLevel3","HevcLevel31","HevcLevel4","HevcLevel41","HevcLevel5","HevcLevel51","HevcLevel52","HevcLevel6","HevcLevel61","HevcLevel62"],"Direction":"Encoder","SupportedColorFormats":["yuv420p","yuvj420p","yuv422p","yuvj422p","yuv444p","yuvj444p","gbrp","yuv420p10","yuv422p10","yuv444p10","gbrp10","yuv420p12","yuv422p12","yuv444p12","gbrp12","gray","gray10","gray12"],"CommandGenerator":{},"CodecDeviceInfo":{"Capabilities":{"SupportsHwUpload":false,"SupportsHwDownload":false,"SupportsStandaloneDeviceInit":false,"Supports10BitProcessing":false,"SupportsNativeToneMapping":false},"Adapter":0,"Name":"Software Codec","Desription":"Software Codec","DeviceId":0,"HardwareContextFramework":"None","VendorId":0},"CodecKind":"Video","MediaTypeName":"H.265 (HEVC)","MaxBitRate":"234 Mbit/s","SupportedColorFormatStrings":["YUV420P","YUVJ420P","YUV422P","YUVJ422P","YUV444P","YUVJ444P","GBRP","YUV420P10","YUV422P10","YUV444P10","GBRP10","YUV420P12","YUV422P12","YUV444P12","GBRP12","GRAY8","GRAY10","GRAY12"],"ProfileAndLevelInformation":[{"Profile":{"ShortName":"HevcProfileMain","Description":"Main Profile","Details":"The Main profile allows for a bit depth of 8-bits per sample with 4:2:0 chroma sampling, which is the most common type of video used with consumer devices.","Id":"HevcProfiles.HevcProfileMain","BitDepths":[8]},"Level":{"ShortName":"HevcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"234 Mbit/s","MaxBitRateDisplay":"234 Mbit/s","Id":"HevcLevels.HevcLevel62","ResolutionRates":["8192x8192@60","8192x4320@120","7680x4320@128","3840x2160@300"],"ResolutionRateStrings":["8192x8192@60","8192x4320@120","7680x4320@128","3840x2160@300"],"ResolutionRatesDisplay":"8192x8192@60, 8192x4320@120, 7680x4320@128, 3840x2160@300"}},{"Profile":{"ShortName":"HevcProfileMain10","Description":"Main 10 Profile","Details":"The Main 10 profile allows for a bit depth of 8-bits to 10-bits per sample with 4:2:0 chroma sampling. allows for improved video quality since it can support video with a higher bit depth than what is supported by the Main profile.[140] Additionally, in the Main 10 profile 8-bit video can be coded with a higher bit depth of 10-bits, which allows improved coding efficiency compared to the Main profile.","Id":"HevcProfiles.HevcProfileMain10","BitDepths":[8,10]},"Level":{"ShortName":"HevcLevel62","Description":"Level 6.2","Ordinal":62,"MaxBitRate":"234 Mbit/s","MaxBitRateDisplay":"234 Mbit/s","Id":"HevcLevels.HevcLevel62","ResolutionRates":["8192x8192@60","8192x4320@120","7680x4320@128","3840x2160@300"],"ResolutionRateStrings":["8192x8192@60","8192x4320@120","7680x4320@128","3840x2160@300"],"ResolutionRatesDisplay":"8192x8192@60, 8192x4320@120, 7680x4320@128, 3840x2160@300"}}],"Id":"V-E-libx265","Name":"x265 Software Encoder","SecondaryFramework":"None","IsEnabledByDefault":false,"DefaultPriority":0},"3: MPEG-4 part 2 Software Encoder":{"FrameworkCodec":"mpeg4","IsHardwareCodec":false,"SupportsParameters":false,"CompatibleDecoderFrameworks":[],"VideoMediaType":"mpeg4","ProfilesWithLevel":[],"SupportedProfiles":[],"SupportedLevels":[],"Direction":"Encoder","SupportedColorFormats":[],"CommandGenerator":{},"CodecDeviceInfo":{"Capabilities":{"SupportsHwUpload":false,"SupportsHwDownload":false,"SupportsStandaloneDeviceInit":false,"Supports10BitProcessing":false,"SupportsNativeToneMapping":false},"Adapter":0,"Name":"Software Codec","Desription":"Software Codec","DeviceId":0,"HardwareContextFramework":"None","VendorId":0},"CodecKind":"Video","MediaTypeName":"MPEG-4","SupportedColorFormatStrings":[],"ProfileAndLevelInformation":[],"Id":"V-E-mpeg4","Name":"MPEG-4 part 2 Software Encoder","SecondaryFramework":"None","IsEnabledByDefault":false,"DefaultPriority":0},"4: MPEG-4 part 2 (MS Variant 3) Software Encoder":{"VideoMediaType":"msmpeg4v3","FrameworkCodec":"msmpeg4","SupportsParameters":false,"IsHardwareCodec":false,"CompatibleDecoderFrameworks":[],"ProfilesWithLevel":[],"SupportedProfiles":[],"SupportedLevels":[],"Direction":"Encoder","SupportedColorFormats":[],"CommandGenerator":{},"CodecDeviceInfo":{"Capabilities":{"SupportsHwUpload":false,"SupportsHwDownload":false,"SupportsStandaloneDeviceInit":false,"Supports10BitProcessing":false,"SupportsNativeToneMapping":false},"Adapter":0,"Name":"Software Codec","Desription":"Software Codec","DeviceId":0,"HardwareContextFramework":"None","VendorId":0},"CodecKind":"Video","MediaTypeName":"MPEG-4 part 2 Microsoft variant version 3","SupportedColorFormatStrings":[],"ProfileAndLevelInformation":[],"Id":"V-E-msmpeg4","Name":"MPEG-4 part 2 (MS Variant 3) Software Encoder","SecondaryFramework":"None","IsEnabledByDefault":false,"DefaultPriority":0},"5: libvpx VP8":{"MinConstantRateFactor":4,"MaxConstantRateFactor":63,"FrameworkCodec":"libvpx","IsHardwareCodec":false,"SupportsParameters":false,"CompatibleDecoderFrameworks":[],"VideoMediaType":"vp8","ProfilesWithLevel":[{"Profile":"Vp8Profile0","Level":"Vp8levelDefault"}],"SupportedProfiles":["Vp8Profile0"],"SupportedLevels":["Vp8levelDefault"],"Direction":"Encoder","SupportedColorFormats":[],"CommandGenerator":{},"CodecDeviceInfo":{"Capabilities":{"SupportsHwUpload":false,"SupportsHwDownload":false,"SupportsStandaloneDeviceInit":false,"Supports10BitProcessing":false,"SupportsNativeToneMapping":false},"Adapter":0,"Name":"Software Codec","Desription":"Software Codec","DeviceId":0,"HardwareContextFramework":"None","VendorId":0},"CodecKind":"Video","MediaTypeName":"VP8","SupportedColorFormatStrings":[],"ProfileAndLevelInformation":[{"Profile":{"ShortName":"Vp8Profile0","Description":"Profile 0","Details":"For non-zero values the encoder increasingly optimizes for reduced complexity playback on low powered devices at the expense of encode quality. For example using 1 tells the encoder only to use only bi-linear sub pixel filtering and a simplified loop filter. In general most users will want to set a value of 0 or ignore this parameter unless they are encoding high resolution content and require playback on very low power devices.","Id":"Vp8Profiles.Vp8Profile0","BitDepths":[8]},"Level":{"ShortName":"Vp8levelDefault","Description":"Default Level","Ordinal":0,"Id":"Vp8Levels.Vp8levelDefault","ResolutionRates":[],"ResolutionRateStrings":[],"ResolutionRatesDisplay":""}}],"Id":"V-E-libvpx","Name":"libvpx VP8","SecondaryFramework":"None","IsEnabledByDefault":false,"DefaultPriority":0}},"EncodingOptions":{"EncodingThreadCount":-1,"ExtractionThreadCount":1,"DownMixAudioBoost":2,"EnableThrottling":false,"ThrottleBufferSize":120,"ThrottleHysteresis":8,"ThrottlingMethod":"BySegmentRequest","H264Crf":23,"EnableHardwareEncoding":true,"EnableSubtitleExtraction":true,"CodecConfigurations":[],"HardwareAccelerationMode":1,"EnableHardwareToneMapping":false,"EnableSoftwareToneMapping":false},"DetectionOutputs":{"Vaapi":{"CodecProviderName":"Vaapi","StandardError":"ffdetect version 5.0.0-emby_2022_05_27-u1 Copyright (c) 2018-2022 softworkz for Emby LLC\n built with gcc 8.3.0 (crosstool-NG 1.24.0)\n configuration: --cc=x86_64-emby-linux-gnu-gcc --prefix=/home/embybuilder/Buildbot/x64/ffmpeg-x64/staging --disable-alsa --disable-debug --disable-doc --disable-ffplay --disable-libpulse --disable-libxcb --disable-vdpau --disable-xlib --enable-chromaprint --enable-fontconfig --enable-gnutls --enable-gpl --enable-iconv --enable-libaribb24 --enable-libass --enable-libdav1d --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libzvbi --enable-pic --enable-version3 --enable-libtesseract --enable-cuda-llvm --enable-cuvid --enable-libdrm --enable-libmfx --enable-nvdec --enable-nvenc --enable-vaapi --enable-opencl --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --enable-shared --disable-static --pkg-config=pkg-config --pkg-config-flags=--static --extra-libs='-lm -lstdc++ -pthread'\n libavutil 57. 19.100 / 57. 19.100\nBegin GetVaAdapterInfo\nFound 19 device entries\nBegin get_nodes\nFound 3 drm entries\nEnd GetVaAdapterInfo\n\n","Result":{
"ProgramVersion": {
"Version": "5.0.0-emby_2022_05_27-u1",
"Copyright": "Copyright (c) 2018-2022 softworkz for Emby Llc",
"Compiler": "gcc 8.3.0 (crosstool-NG 1.24.0)",
"Configuration": "--cc=x86_64-emby-linux-gnu-gcc --prefix=/home/embybuilder/Buildbot/x64/ffmpeg-x64/staging --disable-alsa --disable-debug --disable-doc --disable-ffplay --disable-libpulse --disable-libxcb --disable-vdpau --disable-xlib --enable-chromaprint --enable-fontconfig --enable-gnutls --enable-gpl --enable-iconv --enable-libaribb24 --enable-libass --enable-libdav1d --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libzvbi --enable-pic --enable-version3 --enable-libtesseract --enable-cuda-llvm --enable-cuvid --enable-libdrm --enable-libmfx --enable-nvdec --enable-nvenc --enable-vaapi --enable-opencl --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --enable-shared --disable-static --pkg-config=pkg-config --pkg-config-flags=--static --extra-libs='-lm -lstdc++ -pthread'"
},
"Devices": [
{
"DeviceIndex": 0,
"DeviceInfo": {
"VendorName": "Intel Corporation",
"DeviceName": "CometLake-S GT2 [UHD Graphics 630]",
"SubsytemVendorName": "Lenovo",
"VendorId": 32902,
"DeviceId": 39880,
"SubsytemVendorId": 6058,
"SubsytemDeviceId": 12650,
"DevPath": "/sys/bus/pci/devices/0000:00:02.0",
"DrmCard": "/dev/dri/card0",
"DrmRender": "/dev/dri/renderD128",
"IsEnabled": 1,
"IsBootVga": 1,
"Error": {
"Number": -1,
"Message": "Failed to open the drm device /dev/dri/renderD128"
}
}
}
],
"Log": [
{
"Level": 40,
"Category": 0,
"Message": "Found 19 device entries"
}
]
}
 
,"ExitCode":0},"QuickSyncCodecProvider":{"CodecProviderName":"QuickSyncCodecProvider","StandardError":"ffdetect version 5.0.0-emby_2022_05_27-u1 Copyright (c) 2018-2022 softworkz for Emby LLC\n built with gcc 8.3.0 (crosstool-NG 1.24.0)\n configuration: --cc=x86_64-emby-linux-gnu-gcc --prefix=/home/embybuilder/Buildbot/x64/ffmpeg-x64/staging --disable-alsa --disable-debug --disable-doc --disable-ffplay --disable-libpulse --disable-libxcb --disable-vdpau --disable-xlib --enable-chromaprint --enable-fontconfig --enable-gnutls --enable-gpl --enable-iconv --enable-libaribb24 --enable-libass --enable-libdav1d --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libzvbi --enable-pic --enable-version3 --enable-libtesseract --enable-cuda-llvm --enable-cuvid --enable-libdrm --enable-libmfx --enable-nvdec --enable-nvenc --enable-vaapi --enable-opencl --enable-cross-compile --cross-prefix=x86_64-emby-linux-gnu- --arch=x86_64 --target-os=linux --enable-shared --disable-static --pkg-config=pkg-config --pkg-config-flags=--static --extra-libs='-lm -lstdc++ -pthread'\n libavutil 57. 19.100 / 57. 19.100\nBegin GetVaAdapterInfo\nFound 19 device entries\nBegin get_nodes\nFound 3 drm entries\nEnd GetVaAdapterInfo\nBegin GetVaAdapterInfo\nFound 19 device entries\nBegin get_nodes\nFound 3 drm entries\nEnd GetVaAdapterInfo\nBegin GetVaAdapterInfo\nFound 19 device entries\nBegin get_nodes\nFound 3 drm entries\nEnd GetVaAdapterInfo\nBegin GetVaAdapterInfo\nFound 19 device entries\nBegin get_nodes\nFound 3 drm entries\nEnd GetVaAdapterInfo\n\n","Result":{
"ProgramVersion": {
"Version": "5.0.0-emby_2022_05_27-u1",

I think (from what I've read to other users) that it may be a permissions issue.

 

 

Another issue that I have discovered (I have done all kinds of tests) is that the vainfo gives me different values with the LXC by default, than if I install the drivers:

DEFAUT

 

After installing the drivers (https://www.linuxfordevices.com/tutorials/ubuntu/install-intel-graphic-drivers)

 

For Emby, is the difference between the two screens important?

Thank you very much as always for your support and help.

 

 

Edited October 27, 2022 by LeidenSpain

[Luke 42077]

HI, does this topic help?

 

[LeidenSpain 33]

Hi,

 

Thanks for answering.

I already saw that answer, but it was talking about CUDA.
I have found something similar, but I don't quite understand how to apply it (it's from the PROXMOX forum)

https://forum.proxmox.com/threads/using-intel-quick-sync-inside-container.114502/

Quote

After mapping the video and render group into the container it seems to be detected

This was done by running the following commands getent group video | cut -d: -f3 and getent group render | cut -d: -f3 on the host and in the container and mapping them using the config file and /etc/subuid and /etc/subgid

 

Regards

Edited October 27, 2022 by LeidenSpain

[Luke 42077]

Are you able to test the native package for comparison purposes?

[LeidenSpain 33]

On 10/31/2022 at 7:53 AM, Luke said:

Are you able to test the native package for comparison purposes?

Hi,

 

What are you talking about?
To a machine with ubuntu and install emby directly?

I already did it and it still does not show me the acceleration options

 

But tell me if you want me to do a specific test and I'll do it

 

Regards

Edited November 1, 2022 by LeidenSpain

[Luke 42077]

14 hours ago, LeidenSpain said:

Hi,

 

What are you talking about?
To a machine with ubuntu and install emby directly?

I already did it and it still does not show me the acceleration options

 

But tell me if you want me to do a specific test and I'll do it

 

Regards

@LeidenSpain can you please attach the emby server and hardware detection log files from that Ubuntu test? Thanks.

[LeidenSpain 33]

18 hours ago, Luke said:

@LeidenSpain can you please attach the emby server and hardware detection log files from that Ubuntu test? Thanks.

Hi,

 

This are the files from the server test with the intel drivers:

 

Regards

embyserver.txthardware_detection-63803003128.txt

[Luke 42077]

OK, @softworkz will take a look at this. Thanks.

[softworkz 5066]

On 11/1/2022 at 7:49 AM, LeidenSpain said:

On 10/31/2022 at 7:53 AM, Luke said:

Are you able to test the native package for comparison purposes?

What are you talking about?
To a machine with ubuntu and install emby directly?

He didn't mean to install Emby on "a" machine directly but on "the" host machine that is hosting the proxmox thing.

What I can say is that driver installation is not needed in case of Intel HW because Emby includes all the drivers already.

I know nothing about proxmox though, and I'm afraid, but can't tell you what is needed to get it working in such VM/container.

[LeidenSpain 33]

2 minutes ago, softworkz said:

He didn't mean to install Emby on "a" machine directly but on "the" host machine that is hosting the proxmox thing.

What I can say is that driver installation is not needed in case of Intel HW because Emby includes all the drivers already.

I know nothing about proxmox though, and I'm afraid, but can't tell you what is needed to get it working in such VM/container.

uufff... it's just that I'm afraid to touch the proxmox host, it's not going to get any worse.

Thanks for the info about the intel driver, since seeing that the profiles are increased with the official driver, I didn't know if that was important.

Personally I think it's something about the user's permissions with the proxmox host, but it was in case you know what problem emby has, to try to guide the search.

[softworkz 5066]

1 minute ago, LeidenSpain said:

uufff... it's just that I'm afraid to touch the proxmox host, it's not going to get any worse.

What I can tell is that the Emby installation is clean and isolated. It doesn't change or add any files to the system folders. It brings everything it needs on its own.

It will add the Emby user to the video group and register Emby Server as a system service (and reverts that when you uninstall).

In the past, installing to the host machine has proven to be useful in many such cases for troubleshooting as those are installations where we can provide help.

[LeidenSpain 33]

1 minute ago, softworkz said:

What I can tell is that the Emby installation is clean and isolated. It doesn't change or add any files to the system folders. It brings everything it needs on its own.

It will add the Emby user to the video group and register Emby Server as a system service (and reverts that when you uninstall).

In the past, installing to the host machine has proven to be useful in many such cases for troubleshooting as those are installations where we can provide help.

ok, well, I'll do it and when I have a while I'll do it

[Luke 42077]

14 minutes ago, LeidenSpain said:

ok, well, I'll do it and when I have a while I'll do it

That would be great, thanks !

[softworkz 5066]

7 minutes ago, LeidenSpain said:

ok, well, I'll do it and when I have a while I'll do it

When you are skeptical, you can just extract the Debian package (which you will install when your host is Ubuntu) and you'll be able to see exactly what it installs and that all binaries get installed to /opt/emby-server. You can also see exactly what the installation does and you'll be able to verify that it's reverted on uninstallation.

[LeidenSpain 33]

Simply that as my knowledge in proxmox is fair, I prefer to touch the host as little as possible.
But if later it can be erased as if nothing, it's just spending a while

[LeidenSpain 33]

Hi,

 

Emby installed on the host server, and the transcodification is running:

 

Then, is something with the LXC machine, but I don't know what I can check to discover the problem.

[Luke 42077]

Thanks for testing that. I think you need to configure proxmox so that it will have access to the Gpu

 

[LeidenSpain 33]

4 minutes ago, Luke said:

Thanks for testing that. I think you need to configure proxmox so that it will have access to the Gpu

 

yes, I think the same: there is something that does not give access to the GPU. But I'm supposed to have it right (but obviously I don't).

Can you think of any tests I can do on the virtual machine to see what is missing?

Now let's see how I uninstall emby from the host : Done (or I think)

[softworkz 5066]

Remember that Emby is running as a different user (usually 'emby'), so when you work on the command line inside the container, and vainfo is working, then it means that the user context you are logged in with has access to the GPU, but not necessarily Emby (as the 'emby' user).

[LeidenSpain 33]

1 hour ago, softworkz said:

Remember that Emby is running as a different user (usually 'emby'), so when you work on the command line inside the container, and vainfo is working, then it means that the user context you are logged in with has access to the GPU, but not necessarily Emby (as the 'emby' user).

That is, when I tried vainfo in the container, it used the root user
But then, emby as an app, it's using another user....

Well, of course, this is very important information.

What all the information I find talks about the transfer of permissions.
Of course, not everything is information for emby, but from other platforms that have given the same problem.

 

I have 25 tabs with information about proxmox, emby, ubuntu, drivers,.... 

[softworkz 5066]

@LeidenSpain - Were you able to resolve these issues?

[LeidenSpain 33]

1 hour ago, softworkz said:

@LeidenSpain - Were you able to resolve these issues?

Nothing, impossible.
I have tried everything I have seen, read, videos, tutorials, tests... even right now I am reinstalling proxmox after touching it so much.

[softworkz 5066]

I'm sorry to hear that, unfortunately I don't have any knowledge that could be of help here...

[Luke 42077]

4 hours ago, LeidenSpain said:

Nothing, impossible.
I have tried everything I have seen, read, videos, tutorials, tests... even right now I am reinstalling proxmox after touching it so much.

Let us know if you find anything.

[LeidenSpain 33]

okay,.
If I find out what exactly is going on I will comment.

The other option is not to use a CT and do it with a VM