Search results

My VMs have "bios: ovmf" In my case setting "mitigations=off" did the trick but didn't make me happy

When I setup 1 VM per host I used to disable KSM on the node following this guide: https://pve.proxmox.com/wiki/Kernel_Samepage_Merging_(KSM)

@jens-maus have you tried to disable KSM on top of "mitigations=off" before VM start? in my setup there is no memory pressure within the VM, so KSM in inactive state

on my nodes is "Y" root@063-pve-04347:~# cat /sys/module/kvm_*/parameters/nested Y

Here we go: root@063-pve-04347:~# cat /etc/pve/qemu-server/6303.conf agent: 1 bios: ovmf boot: order=ide2;scsi0 sockets: 2 cores: 24 cpu: host numa: 1 ide2: none,media=cdrom machine: pc-i440fx-8.0 memory: 147456 meta: creation-qemu=8.0.2,ctime=1687984201 name: srv-term-mng.domain net0...

In our environment we so exactly the same. CPU spikes and ICMP ping losses + novnc console freeze with increasing number of RDP users logging into W2019. However setting mitigations=off helped (>50 users work fine on each W2019 vm) One more interesting thing. We could not reproduce an issue...

For the record: I had to do the following: 1. nano /etc/kernel/cmdfile -> root=ZFS=rpool/ROOT/pve-1 boot=zfs mitigations=off 2. proxmox-boot-tool refresh 3. reboot 4. Check with lscpu

R u sure it is correctly applied? Check with lscpu. Should be like this: root@063-pve-04347:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s)...

We also noticed that problem appears more when >64Gb ram allocated (especially 128 and more) and more than 24 vCPUs P.S as I mentioned in another thread, setting "mitigations=off" helped (as workaround only!)

+1 for supporting 5.15 kernel with PVE 8

In my cluster with 3 pve 8, 6.2 kernel, vm 100% CPU spikes,vm packet loss and rare complete freeze, setting “mitigations=off” helped

Agreed. Its not an option for me either

In my case “mitigations=off” helped with freezes on PVE8 with 6.2 kernel

any progress on sorting this spam out?(

Wrong guest memory report by balloon with fresh PVE 8.x and fresh Windows 2019 as guest - Fresh PVE 8 - Fresh Windows Server 2019 as guest - No software but latest Virtio drivers (0.1.229) + balloon service + qemu Guest Agent

I made one of my nodes NFS server (10Gb, NFS exported from ZFS storage with SSD disks) I connected 12 hosts to that Node (NFS storage) with default NFS settings (v.4.2) nfs: DS-254-NFS-B export /tank254/datastore/slave/nfs64k/id254 path /mnt/pve/DS-254-NFS-B server...

Seems this feature is not often requested and quite tricky to implement and maintain

such feature request has been posted in bug tracker for almost 8 years with no progress https://bugzilla.proxmox.com/show_bug.cgi?id=804

You can follow this tutorial with some changes (journaling -> snapshot) with some help from posts on this forum (try search). We've managed to set it up. It works no really smoothly but works https://pve.proxmox.com/wiki/Ceph_RBD_Mirroring

Thanks for the reply. Yeap, I'm fully aware about the issue with IP setting changes (mainly in Windows) - faced it several times. The question is - is there any significant reason to do so and keep VM "up to date" ? For example: may be there are relations between latest Virtio drivers (for all...