One more observation:
Disabling KSM requires rebooting the host because stopping KSM service (and/or disabling it) does not really stop it.
ksmd becomes ghost and cannot be killed (I didnt manage to kill it)
This screen shows: kernel with mitigations=off and ksdtuned stopped and disabled (but...
Could you try to continuously ping your VM (from any other device in network) like gateway?
Huge ping delay spikes are common for the topic issue. If you don't have any then probably there is something else interfere
P.S. Do not ping from another VM on the same host
P.S.S In my case before...
If I am not mistaken mitigations=off is not applied
What filesystem behind your root partition?
In my case (zfs) i had to edit cmdfile file
Check this post:
https://forum.proxmox.com/threads/disable-spectre-meltdown-mitigations.112553/post-485863
If on your systems KSM is in use then try to disable it with "systemctl disable --now ksmtuned" on top of
and cross-check that mitigations are really off with lscpu
@t.lamprecht
Is there any progress on sorting out the degradation in KSM and huge performance (CPU 100% spikes) loss in Windows guests with 6.2 kernels?
For non-root limited user I would like to limit view to pool only in pve cluster. Is there any way to disable datacenter view or/and set another view (pool view) for given user as default
The idea behind is to hide number of cluster nodes and their names
Thanks in advance
I can confirm that with 6.2.16-14 problem still exists
Setting "mitigations=off" the only solution
@ProxmoxTeam
Any progress on this issue?
P.S Taking into consideration that KSM with kernel 6.x is broken on dual socket boards +1 vote to release 5.15 kernel
I had 3 nodes cluster with CEPH installed (several OSDs on each node) in network 10.63.210.0/24 for PVE (1Gb) and 10.10.10.0/24 for CEPH (10Gbe).
It was OK until I added 4-th node to PVE cluster only from another network 10.63.200.0/24 (no CEPH/OSD on that node). PVE cluster is happy, CEPH...