Recent content by fabian

you need to upgrade qemu-server to 9.1.4, not pve-manager..

the benefits of a) are - better (human) readability (compared to more involved escaping) - no need for migrating between old and new formats - compat with PVE/.. that use identical schemes (we share code across products) the main downsides are - if you try to store those files on systems that...

qemu-server 9.1.4 (currently making its way through the repositories) contains the fix.

try the 6.17.9 kernel and please report back!

der kernel hat (de facto) keine abhaengigkeiten..

der vorherige kernel wird nicht automatisch deinstalliert, und du kannst beliebige installierte kernel versionen pinnen wenn ein DKSM modul mal noch nicht mit der neuesten series kompatibel ist: https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_kernel_pin

the 6.17.9 kernel is now on pve-test, please ensure you also have amd64-microcode and latest system firmware ("BIOS") updates installed if your system has an AMD Zen 5 based CPU: see "AMD Zen5 CPU issue with RDSEED instruction on kernels newer 6.17.9" in...

I think I found the offending commit, a fix for it is in 6.17.5, we already have a 6.17.9 based kernel in internal testing that should hit the public repositories this week..

okay, those should not be affected by the quirk setting..

similar symptoms reported in https://bugzilla.proxmox.com/show_bug.cgi?id=7249

thanks. so between 6.17.2 and 6.17.4 a quirk for a specific NVME model was added.. you could post "lspci -vvv" for both NVMEs in your system? thanks!

thanks! so that one seems to be PCIe/nVME related ( as opposed to the CPU stuck messages by other users). what kind of nVME is this? which previous kernel version worked for you on this system?

because it's a Linux based piece of software, and Linux doesn't care about such things (paths are sequences of bytes). shell handling does require extra attention, that's why tools like find and xargs have special modes: $ find . -iname "*001D9C7A*" -print0 | xargs -0 ls -lha -rw-r--r-- 1...

https://bugzilla.proxmox.com/show_bug.cgi?id=7244

there are no plans for this at the moment as far as I know. to mirror an APT repository (correctly), you need to do partial syncs in the right order and have some safety checks built-in, or have a way to synchronize mirroring and repository updates, no matter whether you are using rsync or plain...