qm config <vmid>root@pmx-01:~# qm config 101bios: ovmfboot: order=virtio0;ide0;ide1cores: 2efidisk0: local-lvm:vm-101-disk-0,efitype=4m,pre-enrolled-keys=1,size=4Mide0: local:iso/virtio-win-0.1.240.iso,media=cdrom,size=612812Kide1: local:iso/Windows11_23H2.iso,media=cdrom,size=5529856Kmachine: pc-q35-9.0memory: 4096meta: creation-qemu=9.0.0,ctime=1722265584net0: e1000=BC:24:11:9B:A8:46,bridge=vmbr0,firewall=1numa: 0ostype: win11scsihw: virtio-scsi-pcismbios1: uuid=1d84de9f-fb9c-467d-9682-20d71e5d616dsockets: 1tpmstate0: local-lvm:vm-101-disk-1,size=4M,version=v2.0virtio0: local-lvm:vm-101-disk-2,cache=writethrough,iothread=1,size=150Gvmgenid: ab8536b6-eadf-4939-bee6-240c5527386cide1 which is the Windows installer , so it booted initially fine allowing you to set it up correctly (with all virtio drivers) so it now boots correctly from the virtio0 disk.virtio0 disk already has Windows installed on it, it probably won't boot until you actually setup the virtio drivers from within Windows. (That would be catch-22, but is doable).I did. Your advice worked. But as I said, the first time I did this, I didn't have this issue.
You obviously either didn't read my post or didn't understand it correctly. The "first time" you did not have this issue, because then you correctly attached the Windows 11 installer to the VM, this time you did not!
I mean, the first time I did this, I did not have to do any of the driver installation; it booted right up, and Windows installed without an issue.
