Opt-in Linux 6.17 Kernel for Proxmox VE 9 available on test & no-subscription

[bossanova808]

I don't think it's a abi issue then. You could allow access with:

/run/systemd/journal/dev-log r,

inside the profile.

Thank you Fiona, that indeed appears to quieten the log entries. I assume allowing it to read that log doesn't really pose any significant risk, so seems a good solution,

 

[SInisterPisces]

Nice, edac memory error reporting also now works on Intel 12th-14th gen parts in W680 motherboards with ECC memory.

This is exciting. Thanks for pointing it out.

Just to clarify, this is actual marketed ECC RAM, right? Not just the on-die ECC features that all DDR5 has?

 

[Ramalama]

This is exciting. Thanks for pointing it out.

Just to clarify, this is actual marketed ECC RAM, right? Not just the on-die ECC features that all DDR5 has?

On-Die ECC has no error reporting or edac or anything. On Die ECC is just for the memory module itself due to the high frequency it was simply needed.

Im sure they talk about "real" ECC, since normal ECC has error reporting (sometimes not), but EDAC Support anyway.

 

[SInisterPisces]

On-Die ECC has no error reporting or edac or anything. On Die ECC is just for the memory module itself due to the high frequency it was simply needed.

Im sure they talk about "real" ECC, since normal ECC has error reporting (sometimes not), but EDAC Support anyway.

What a lovely and succinct explanation. Thanks.

 

[devedse]

Has anyone gotten FFMPEG hardware encoding working yet on the B50? I've tried it on kernel 6.17 but it won't work.

I downloaded the Uranite FFMPEG build here:
https://github.com/Uranite/FFmpeg-Builds-SVT-AV1-PSY/releases

When I run:

./ffmpeg -i omd.mkv -c:v h264_qsv -preset veryfast -global_quality 23 omd_output.mkv

I see:

[h264_qsv @ 0x5fb0df128640] Error creating a MFX session: -9.
[vost#0:0/h264_qsv @ 0x5fb0df1275c0] [enc:h264_qsv @ 0x5fb0df0c8680] Error while opening encoder - maybe incorrect parameters such as bit_rate, rate, width or height.
[vf#0:0 @ 0x5fb0df12d500] Error sending frames to consumers: Unknown error occurred
[vf#0:0 @ 0x5fb0df12d500] Task finished with error code: -1313558101 (Unknown error occurred)
[vf#0:0 @ 0x5fb0df12d500] Terminating thread with return code -1313558101 (Unknown error occurred)
[vost#0:0/h264_qsv @ 0x5fb0df1275c0] [enc:h264_qsv @ 0x5fb0df0c8680] Could not open encoder before EOF
[vost#0:0/h264_qsv @ 0x5fb0df1275c0] Task finished with error code: -22 (Invalid argument)
[vost#0:0/h264_qsv @ 0x5fb0df1275c0] Terminating thread with return code -22 (Invalid argument)
[out#0/matroska @ 0x5fb0df267940] Nothing was written into output file, because at least one of its streams received no packets.

 

[alex.76]

I've been running some tests for the past 3-4 days on our new server before putting it into production and migrating to ESXi.

Having poor performance on ZFS, I'm currently testing btrfs to find the best solution between performance and data integrity.

I'm not really sure what was changed with Kernel 6.17 (if it's solely related to BTRFS), but I've seen a significant increase in throughput/IOPS and latency benchmarks without touching anything at all apart from the update.

Host:
EPYC 9475F - DDR5 ECC REG 6400 - 4x NVME Gen5 Kingston DC3000ME 7.86 TB
Storage: RAID10 BTRFS (created after the setup, default option upon creation)

VM: Host CPU - SCSI Single - No cache / aio_uring / IOthreads ON

Capture from Windows VM just before the kernel update and the other just after the reboot.




CPU level at Passmark I have almost the same figures and which are practically the same as a Passmark executed directly on the host (127k multi thread and 4129 in single thread)