Whole system rebooting when I restart a particular Windows 10 VM from host

marcosscriven

Member
Mar 6, 2021
136
11
23
I've found that selecting "restart" on a particular Windows 10 VM from Proxmox UI will freeze and restart the whole system. To start with I thought I selected the wrong thing, and restarted the node. However, I've found this is reproducible.

The only different log I get from a normal VM restart is this:

Code:
[Tue Jun  4 10:01:28 2024] vfio-pci 0000:01:00.0: enabling device (0000 -> 0003)

And then the whole system hangs/restart.

What's super odd is that I cloned the VM, and tried the same with that, and it works fine! I've repeated this many times with both the original and the clone, and get the same behaviour every time.

Now I suppose I can just keep the clone and delete the old one, but it seems like a very strange issue to me and would preferably like to understand what's happening

The only thing I did notice that if I didn't pass through the USB controller, the issue didn't happen (but as I say, this wasn't a problem on the clone). The very same controller can be passed into another Windows VM (obviously at a different time) and there's no resetting issue.

Also - restarting or resetting from within the Windows VM guest has no issue either.


Conf:

Code:
agent: 1
balloon: 0
bios: ovmf
boot: order=scsi0;net0
cores: 16
cpu: host
efidisk0: local-lvm:vm-107-disk-0,efitype=4m,pre-enrolled-keys=1,size=4M
hostpci0: 0000:01:00,pcie=1,rombar=0,x-vga=1
hostpci1: 0000:15:00.0,pcie=1,rombar=0
machine: pc-q35-8.1
memory: 32768
meta: creation-qemu=8.1.5,ctime=1711703824
name: w10-gaming
net0: virtio=BC:24:11:32:A1:03,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsi0: local-lvm:vm-107-disk-1,cache=writeback,discard=on,iothread=1,size=128G,ssd=1
scsi1: local-lvm:vm-107-disk-2,backup=0,cache=writeback,discard=on,iothread=1,size=512G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=1f97872f-1842-44e6-bc20-5413f7b77912
sockets: 1
vmgenid: d7f93b88-0c88-4cef-82df-28d2361fe8ab

As you can see, 01:00.0 is the GPU.
 
Last edited:
Sorry to bump this - but any ideas where to start on this one please? I found that eventually this started affecting even the clone.

So no idea what's happening specifically with a "restart" of VM from Proxmox host.
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!