On 11/8/21 4:12 pm, Gerd Hoffmann wrote: > Hi, > >> I amended my script to have: >> >> -drive if=none,id=sd00,file=disk.img,format=raw \ >> -device virtio-scsi-pci,id=scsi \ >> -device scsi-hd,bus=scsi.0,drive=sd00 \ > > That switches storage from ide to virtio-scsi. > > Which is a good idea from the performance point of view. Will obviously > also workaround ide problems. But might fail now due to virtio-scsi > driver not being part of your initrd. >
Thank you James & Gerd, Your suggestions & comments led me to reconsider the contents of the initrd and the problem is now fixed. I had been using an initrd that worked perfectly in a non-UEFI boot and half worked with UEFI boot (the working half being when code was patched). However when I generated a completely new initrd after installing a new system in UEFI mode, I could see many virtio modules being added which were not part of the old initrd I had been using. Booting with the new initrd works perfectly in all boot modes using OVMF files created without any code patching. Is there a particular procedure to withdraw my patch request, or does it die a quiet death by being ignored now? Thanks again, chris -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#79099): https://edk2.groups.io/g/devel/message/79099 Mute This Topic: https://groups.io/mt/84767423/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-