Search results

I am kinda frustrated that this is turned on by default and there isn't even a warning: https://pve.proxmox.com/wiki/Kernel_Samepage_Merging_(KSM) This was totally screwing our VM. And I mean really badly, 4s freezes every minute.

I was testing that as well, seems to do something, but not solve the issue, this would be 100% ksm, it seems. Thank you very much.

80 thread, 76 allocated to VM, 2 to mini test VM, 2 left to Proxmox. I tried just now. Disabling numa balancing didn't help. But disabling ksm and unmerging pages may have solved it. Maybe too soon to say. But it looks promising.

Load is very low 5-10 (for 68 threads in VM). So I doubt it can be related to any CPU provisioning, high load etc. Also no CPU soft locks. Wrong terminology isn't really the issue here.

No ideas?

I wrote a script that does timestamp in a loop on the VM: Previous: 1744891845 Current : 1744891849 Diff : 4 seconds There is no sleep nothing between commands and there are basically 4+ seconds lags in loop. So VM basically freezes.

I rebooted and after around 18 hours, it was back:

Changing tread assignments to follow numa may have some effect, but it does not solve the issue.

Adding info: System has 2 CPUs and numa is enabled. VM uses threads from both CPUs.

For some reason it got put into German thread, can admin move this? Thank you.

I have several Proxmox servers and on 2 separate servers running Proxmox 8.3.x, I have serious issues with my VMs temporarily stuttering/freezing. It was first notice by high pings repeating in 60-90 seconds patterns. But after running echo date in loop, I am pretty certain that this not a...

Network unrechable inside VM: qm config 100 boot: order=scsi0;net0 cores: 20 memory: 409600 name: ... net0: e1000=1E:75:96:30:3F:8F,bridge=vmbr0 numa: 0 onboot: 1 ostype: l26 scsi0: local-lvm:vm-100-disk-0,size=512G scsihw: virtio-scsi-pci smbios1: uuid=ea4211f3-5fb1-4966-a024-db9eeb8c6d9b...