how can I pin the kernel if the one from proxmox-boot-tool is no longer displayed after the update?Kernel is not removed during update,only if you use autoremove command.
proxmox-boot-tool kernel list
Manually selected kernels:
None.
Automatically selected kernels:
5.15.85-1-pve
6.1.10-1-pve
6.1.14-1-pve
proxmox-boot-tool kernel list
Manually selected kernels:
None.
Automatically selected kernels:
5.15.85-1-pve
6.1.10-1-pve
6.1.14-1-pve
6.1.2-1-pve
Pinned kernel:
6.1.2-1-pve
how can I pin the kernel if the one from proxmox-boot-tool is no longer displayed after the update?
apt list --installed | grep -P 'pve-kernel-\d+.\d+.\d+'
error: out of memory.
Press any key to continue...
[ 0.649534] shpchp 0000:05:01.0: pci_hp_register failed with error -16
[ 0.650047] shpchp 0000:05:01.0: Slot initialization failed
[ 0.652315] shpchp 0000:05:02.0: pci_hp_register failed with error -16
[ 0.652810] shpchp 0000:05:02.0: Slot initialization failed
[ 0.655294] shpchp 0000:05:03.0: pci_hp_register failed with error -16
[ 0.655728] shpchp 0000:05:03.0: Slot initialization failed
[ 0.657520] shpchp 0000:05:04.0: pci_hp_register failed with error -16
[ 0.657918] shpchp 0000:05:04.0: Slot initialization failed
[ 0.770160] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 0.772236] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.15.0-67-generic #74-Ubuntu
[ 0.774022] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
[ 0.775519] Call Trace:
[ 0.775715] <TASK>
[ 0.775934] show_stack+0x52/0x5c
[ 0.776246] dump_stack_lvl+0x4a/0x63
[ 0.776859] dump_stack+0x10/0x16
[ 0.777099] panic+0x149/0x321
[ 0.777414] mount_block_root+0x144/0x1dd
[ 0.778023] mount_root+0x10c/0x11c
[ 0.778362] prepare_namespace+0x13f/0x191
[ 0.778721] kernel_init_freeable+0x18c/0x1b5
[ 0.779072] ? rest_init+0x100/0x100
[ 0.779365] kernel_init+0x1b/0x150
[ 0.779689] ? rest_init+0x100/0x100
[ 0.780008] ret_from_fork+0x22/0x30
[ 0.780309] </TASK>
[ 0.780570] Kernel Offset: 0x23000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff)
[ 0.781495] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---
amd->amd ? or amd-> intel ? or intel-> amd ?With the installed kernel I have the known problems after live migration with VM'S freezing.
Unfortunately, I can't tell you exactly in which cases this happens. It feels like the direction doesn't matter.amd->amd ? or amd-> intel ? or intel-> amd ?
after some investigation, it seems to only happen if i migrate from intel to amd. all other variants are workingamd->amd ? or amd-> intel ? or intel-> amd ?
what is the cpu model in your vm ?after some investigation, it seems to only happen if i migrate from intel to amd. all other variants are working
those people switched from 5.15 and the issue in the bug report was not about migrations between CPUs from different vendors. The fixes from 5.19 should still be there in 6.1 and 6.2. Please note that in general live migration between CPUs from different vendors is not supported, see the requirements in the docs.after some investigation, it seems to only happen if i migrate from intel to amd. all other variants are working
some ppl solved the problem with switching to 5.19 like discussed here: https://bugzilla.proxmox.com/show_bug.cgi?id=4073
question is: is it save to migrate to 5.19, in fact its EOL
Oh no. I don't know how, but i somehow missed this requirement too bad i've a fresh intel hypervisor ready for the clusterPlease note that in general live migration between CPUs from different vendors is not supported