On Tue, Dec 06, 2022 at 07:25:27PM +0000, Thorsten Glaser wrote: > Hi dann, > > > Could you confirm the last version that worked for you - perhaps > > I have never booted an EFI system before; this VM was the first > time for me, so I do not have a “last version” either way. > > As I said, this does work with BIOS (or at least used to).
OK, then I think there may be multiple conflated issues here. Let's focus on the original use case you described - a VM created with virt-manager using a SCSI controller doesn't work. You tried "lsilogic", but you assume based on a RH report that "virtio-scsi" also does not work. I just tried this on latest sid, and was able to reproduce. "lsilogic" does indeed not work. I also didn't find a way to tell virt-manager to use anything other that "lsilogic". But, when I edited the XML and changed "lsilogic" to "virtio-scsi" (and ran virsh define), the system booted fine. Thorsten - do you have reason that you prefer lsilogic to virtio-scsi? If not, I suggest just using virtio-scsi. I don't know why virt-manager defaults to that - even virt-install seems to default to virtio-scsi. I suggest someone take that up w/ the virt-manager maintainer(s). Now, Vincent me too'd this bug to say that virtio-scsi wasn't working for them, but the version in bullseye did work. Thorsten reported using the version of ovmf that *is* in bullseye and wasn't using virtio-scsi. So whatever Vincent is/was seeing seems like a separate issue. If you are still having a problem Vincent, please report a separate issue. -dann
