Search results

Hello, ppl. I'm having a hard time backing up one of my customers running ProxmoxVE. His ISP is supplying about 15Mb/s speed, but its bad wireless connection so its fluctuating between 5-15Mb or eventualy dropping completely. I have BackupServer on-prem with newly installed ProxmoxBackupServer...

pve-kernel-5.13.19-6-pve seems to be stable, try switching to that with " https://pve.proxmox.com/wiki/Host_Bootloader "

I made bash script for single node solution, checks VMs list one by one every 10 minutes with PING, if VM does not respond, it starts the VM with "qm start ..."

Im running WinServer 2022 with MSSql server 2019 with small database under 10G, the VM crashed regularly, other VM with WinServer 2022 serving as windows fileserver does not crash, meaning on the same Proxmox instance

same here VM created through Proxmox "wizzard" for Win Server 2022

for me it did not work, crash after aprox 2,5 days :(

Okay, nevermind, VM crashed again this morning at 5:15, roughly arround time of previous crashes. Going back to 5.13.x kernell

I didnt migrate anything (just backup to be sure nothing gets broken) but if you need the VM to be running, sure, migrate to secondary node, make changes on the "affected" node and migrate back BUT im not sure if the VM will notice change of CPU's options without reboot (like the disabled...

After disabling NestedVirtualisation ( via /etc/modprobe.d/kvm-intel.conf ), my problematic VM (WinServer 2022, MSsql server) on Xeon W-2125 is running for "1d 14h" and no crashes yet, holding my fingers for this to last... i hope this will narrow down the problematic behaviour for some ppl

on my affected RIG is Intel Xeon W-2125 which is Skylake. I'm gonna test turning OFF the nested option through modprobe options as @apkoval suggested. The problematic VM crushes once per 1-2days arround 5 am

Hello! I also had this issue receltly on of my newly transformed server with Xeon W-2125 (transission to Proxmox) with 7.2 installer. Wierd thing is, that i have 2 guest VMs with Windows 2022 (almost same config (just different cpu and ram ammounts) on the same Host machine, and ONLY the one...