Hello. I have noticed an easily replicated bug with proxmox, which is outlined in the subject. Here are the steps involved in replicating the bug:
1) Install windows 10 enterprise ltsc 2019 using iso obtained directly from microsoft
2) After the operating system is installed, install the virtio drivers and spice agent using the virtio-win-guest-tools installer in the iso so we can connect to the device via spice
3) shut down the vm
4) change the display from default to spice
5) start the vm
6) as the vm attempts to load the operating system, the vm blue screens and automatically restarts.
To be clear, the vm does successfully boot after the first crash occurs, but this initial crash seems to occur each time the display hardware option is changed, but the blue screen only seems to appear when the display is changed to spice from something else. See below video for more info:
https://youtu.be/OPIafV8Zz1c
1) Install windows 10 enterprise ltsc 2019 using iso obtained directly from microsoft
2) After the operating system is installed, install the virtio drivers and spice agent using the virtio-win-guest-tools installer in the iso so we can connect to the device via spice
3) shut down the vm
4) change the display from default to spice
5) start the vm
6) as the vm attempts to load the operating system, the vm blue screens and automatically restarts.
To be clear, the vm does successfully boot after the first crash occurs, but this initial crash seems to occur each time the display hardware option is changed, but the blue screen only seems to appear when the display is changed to spice from something else. See below video for more info:
https://youtu.be/OPIafV8Zz1c
