Recent content by fabian

thanks for the report! nothing in the -8 to -9 diff looks like it could be the culprit, so more likely it's a hard to trigger bug that was there before that version already..

you can use "pvenode cert delete 1" to undo the custom certificate

now on pve-no-subscription

similarly, proxmox-kernel-6.8.12-40-pve fixes it for PVE 8.x

it sounds like you might have typoed/messed up the formatting somehow.. other than locking/protection against concurrent modification, editing manually or via the API doesn't make a difference..

https://bugzilla.kernel.org/show_bug.cgi?id=221801 https://lore.kernel.org/20260801201244.4421-1-andiwild@gmail.com could you maybe also try with the proposed fix and report whether it works to the kernel devs?

you did not understand it correctly. the backend will select the actual (running) machine version based on the creation date. the frontend displays the "oldest" version, because the frontend code does not have the logic to do that mapping. it could display a different string, but the issue is...

https://forum.proxmox.com/threads/web-ui-bug.176731/

please also post the log I requested.

this is not the enterprise support portal, but the community forum. if you want enterprise support, open an enterprise support ticket.

okay, then please do "pct set 999 --mp0 /mnt/nas_media,mp=/mnt/test,shared=1" and retry

could you also check the kernels inbetween? in particular -6 would be interesting, as that is the first of two stable updates in that version range (the second was -7)

no, those two would be the main ones.

no logs on disk does not mean no logs generated. a serial or netconsole, or checking pstore can often help. w.r.t. the changelogs: * update submodules and patches to Ubuntu-7.0.0-28.28i3 - upstream stable changes from 6.18.39 and 7.1.4 - various CVE fixes this means that we updated...

@Frank-75 please post the full migration task log, and the full "pveversion -v" output from both source and target node.