Search results

There´s some Problems with the 6.2 Kernel. Not only Windows-VM´s are affected, we also experienced some weird random behaviours spreaded across different locations. KSM, Qemu, Network-related things etc... Hopefully the 6.2 gets mature as soon as possible.

Done all but does not solve the remaining issue. So, manual deleting was the only way to get rid off the annoying messages in syslog..

yes, on all nodes.

So i deleted these annoying things and it´s silent now. ;)

@auranext did you ever solve this issue?

Just for my case: It was a Windows-Problem -> Disk-Error (in the related VM). Also restoring the VM from Backup does not solve the issue. So i had to boot the VM via Windows-Install Disk and force a checkdisk (found some errors). After that the VM boots up without any issues.... Crazy world...

Thanks, but what is the Solution?

Wow, same here. :eek:

So sollte es aussehen: UUID=354b626f-30f1-4cc6-a3a6-c7192a7eb1ad /mnt/pve/omv-music ext4 defaults 0 0

Hatte ich auch, liegt aber am letzten "1". ändere den Eintrag auf "0", zB.: /dev/sdb /mnt/pve/omv-music ext4 defaults 0 0 Grund: PVE will einen fsck machen, bevor der Mountpoint gemountet wurde. Somit beisst sich die Katze irgendwann in den eigenen Schweif ;)

Same here.

I hope so... ;)

Searched an Host with the same CPU and here it is: root@pbs-dc1:~# 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): 28 On-line CPU(s) list...

This size applies only to our Database Servers... Hmm, mitigations=off is set up everywhere here.

"Just 64GB RAM" because its just an example-VM that doesn´t need more. Single-Socket because the Hardware is on an AMD Milan, this is a Single-Socket-Blade with 48 Cores. CPU-Limit -> simply to limit the VM ;)

There´s a lot of 2019-VMs, but here one Example: agent: 1 bios: ovmf boot: order=scsi0;net0 cores: 12 cpu: host cpulimit: 10 efidisk0: VM_NVMe:vm-2001-disk-3,efitype=4m,pre-enrolled-keys=1,size=528K machine: pc-q35-7.2 memory: 65536 name: REMOVED net0...

Wow, upgraded some different Servers to PVE8 (standalone/ceph-cluster and so on...) and the 2019-VMs (RDS mostly) runs better/faster than with PVE7. The CPU´s are all differently, few old Xeons to modern Xeons, AMD Milans etc..... The only one where they are similar, the CPU-Governor is always...

Upgraded a Testserver PVE7to8 with Co-installed PBS, every seems fine.

So machen wir das auch bei "kleinen" Clustern. Active-Backup funktioniert hier verlässlich, sowohl VM-Traffic, Ceph, Corosync sowieso. Hauptvorteil: Man ist gewissermaßen Switch-Funktionalitäts/Kompatibilitäts-unabhängig.

HW-RAID über Controller, Filesystem ext4.