Proxmox PVE will crash out when Win Server 2025 and MS SQL 2025 is used.

[eatonjb]

I am really new to this, I have a client that I setup a proxmox server with a Windows 2025 server and all the updates, and installed a copy of Microsoft SQL 2025.

After some time, of use. (right now it's only 1 workstation using it) it will crash out the Proxmox server and the user has to reboot the server, and start all over again.

I am at a total lost,

I turned off ballooning memory
turned on NUMA
Running on X86-64-v2-AES
Vertools IO version 0.1.302,
10gig of memory,
SeaBIOS
I440fx 10.0+pve2 (I had it on q35 10.1)
vIOMMU to none.

I am really not sure what else is going on, i have no idea how its crashing the Proxmox VE.

I am really new to this, so if there is anything I can look at or change that is recommended, please let me know. I am clueless on how this crashes the Proxmox host itself.

edit: I am having the user just RDP into the Windows server and try doing his stuff there, it seems stable for some reason, but ill have to wait.

 

[bbgeek17]

Hi @eatonjb, welcome to the forum.

The first thing I would check is the system log:journalctl. There may be some clues there.
If the customer has to manually power-cycle the server, that may indicate that there are messages on the console. If a monitor is not currently connected, it may be worth connecting one and taking a photo of the screen before rebooting the server.

Very often, the symptoms you describe can be hardware-related. Is the server you are using enterprise-grade hardware, or is it more of a home-lab type system?

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[et-ducky]

Right after the next forced restart, I'd read the last messages from the boot that crashed with journalctl -b -1 -p warning (run journalctl --list-boots first to confirm the previous boot was saved). Also compare the host's total RAM with the 10 GB assigned to the VM plus what the host uses itself, and run arc_summary if the VM disk is on ZFS.

Inside Windows, set SQL Server's maximum server memory a few GB below 10 GB.

Drafted with AI, reviewed by me.