Testing a windows 11 iot enterprise ltsc VM and every time I shutdown the server cold when I restart I do not get a display, at first it looks like it's frozen here, but the machine is up and running as I can use remote desktop and get into it.
Failed boots look like this spinning dots
It stops right after the dots on this screen.
This one with the solid circle will boot:
I have to kill -9 the VM then next boot display works again. If I login with remote desktop and shutdown fine it will not boot with console, I have to kill it then it will boot clean that's what I find strange but could explain
A regular win 11 machine with same setting doesn't exhibit these problems...
agent: 1
bios: ovmf
boot: order=scsi0;ide0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
efidisk0: tank0:vm-847-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide0: local:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812K
ide2: local:iso/26100.1.240331-1435.ge_release_CLIENT_IOT_LTSC_EVAL_x64FRE_en-us.iso,media=cdrom,size=4324832K
machine: pc-q35-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1718812397
name: win11iotlts
net0: virtio=BC:24:11:99:F4:FD,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: tank0:vm-847-disk-1,discard=on,iothread=1,size=64G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=963a36a3-1e7c-4e41-bef5-d961346f1b68
sockets: 1
tpmstate0: tank0:vm-847-disk-2,size=4M,version=v2.0
vmgenid: be6cefe8-0ad7-49cd-88bf-0d423ef4c8c3
pve-manager/8.2.2/9355359cd7afbae4 (running kernel: 6.8.8-1-pve)
latest 8.2.2
Very reproducible so should be easy to diagnose report if you are interested... Thank You
Failed boots look like this spinning dots
It stops right after the dots on this screen.
This one with the solid circle will boot:
I have to kill -9 the VM then next boot display works again. If I login with remote desktop and shutdown fine it will not boot with console, I have to kill it then it will boot clean that's what I find strange but could explain
A regular win 11 machine with same setting doesn't exhibit these problems...
agent: 1
bios: ovmf
boot: order=scsi0;ide0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
efidisk0: tank0:vm-847-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
ide0: local:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812K
ide2: local:iso/26100.1.240331-1435.ge_release_CLIENT_IOT_LTSC_EVAL_x64FRE_en-us.iso,media=cdrom,size=4324832K
machine: pc-q35-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1718812397
name: win11iotlts
net0: virtio=BC:24:11:99:F4:FD,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: tank0:vm-847-disk-1,discard=on,iothread=1,size=64G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=963a36a3-1e7c-4e41-bef5-d961346f1b68
sockets: 1
tpmstate0: tank0:vm-847-disk-2,size=4M,version=v2.0
vmgenid: be6cefe8-0ad7-49cd-88bf-0d423ef4c8c3
pve-manager/8.2.2/9355359cd7afbae4 (running kernel: 6.8.8-1-pve)
latest 8.2.2
Very reproducible so should be easy to diagnose report if you are interested... Thank You