I tried that already. Same issue. It only happens mostly on UEFI VMs. And only older VMs. Fresh installed Win10 with 6.1 or 6.2 qm do not have the issue.
It is a Windows 10 Enterprise 21H2 with TSPlus as Terminalserver Addon.
The reboot worked fine in Proxmox 6.x. After the upgrade to 7.x the issues came up. I tried many options, also the pve-edge-kernel.
Hi,
I finally got it fixed (kind of)!
Change OS Type to "other" and the reboot issue is gone for me.
I'm glad that I can reboot my TerminalServers nightly again.
leider gleicher Fehler mit sogar dem neuesten msi:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-qemu-ga/qemu-ga-win-102.10.0-0.el8_5/qemu-ga-x86_64.msi
Ok so I'm using Proxmox since the Version 1.1 and in the early days I used the same scheme you plotted. So a "real" shared storage can only be in cluster mode by using LVM because the SCSI IDs in Linux allow the same storage by managing it via the LVM. So for example, you define one shared VG...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.