OK, given that the edk2 commit in question is correct, I asked specifically for bug-compat ideas on edk2-devel:
http://<email address hidden>
I'll also try to ask IDE and Windows experts for help with figuring out what Windows is waiting for, when it's apparently doing nothing.
As a mid-term mitigation / work-around, I suggest using virtio-block or virtio-scsi for hard disks, and virtio-scsi for CD-ROMs. Windows (7, 8, and 10) can be perfectly well installed from a virtio-scsi CD-ROM to a virtio-scsi or virtio-blk hard disk, as long as the guest has *another* CD-ROM, using IDE or AHCI, and this CD-ROM presents the virtio-win ISO. The only thing the Windows installer *really* has to read from an IDE/AHCI CD-ROM is the virtio-scsi/virtio-block driver, all the rest can work with virtio.
OK, given that the edk2 commit in question is correct, I asked specifically for bug-compat ideas on edk2-devel:
http://<email address hidden>
I'll also try to ask IDE and Windows experts for help with figuring out what Windows is waiting for, when it's apparently doing nothing.
As a mid-term mitigation / work-around, I suggest using virtio-block or virtio-scsi for hard disks, and virtio-scsi for CD-ROMs. Windows (7, 8, and 10) can be perfectly well installed from a virtio-scsi CD-ROM to a virtio-scsi or virtio-blk hard disk, as long as the guest has *another* CD-ROM, using IDE or AHCI, and this CD-ROM presents the virtio-win ISO. The only thing the Windows installer *really* has to read from an IDE/AHCI CD-ROM is the virtio- scsi/virtio- block driver, all the rest can work with virtio.