On Tue, Dec 06, 2022 at 09:21:21PM +0000, Thorsten Glaser wrote: > Hi dann, > > >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 > > Nonono, not quite. > > The original use case: an *EFI* VM with a SCSI controller does not > work. This is what I reported.
Sure, I thought that was implied since this is a UEFI firmware bug. To be clear, my testing was with UEFI boot enabled. > >I just tried this on latest sid, and was able to reproduce. "lsilogic" > >does indeed not work. > > Oh, interesting. That’s got to be a new/different bug. We were on > bullseye, not sid, in case that helps. Do you believe it is new/different because you assumed I was not using a UEFI VM, or some other reason(s)? Note that I tested both bullseye and sid - neither supports it, and there's no evidence we ever did. > >Thorsten - do you have reason that you prefer lsilogic to virtio-scsi? > > Yes: I mostly run operating systems with no or insufficient support > for virtio over the hypervisor interface. (There’s also virtio over > PCI, but my inquiries to the qemu developers how to even access this > led to them eventually agreeing it probably isn’t even implemented > fully yet.) OK, so it sounds like this bug is really a "please enable lsilogic support in OVMF" - as that is the only way to support the guests you mostly run w/ SCSI. Is that accurate? > In the specific case, it was a VM “appliance” imported from some > other virtualisation tools that had a preconfigured Windows, and > the other VM hosts all use lsilogic for that. I trimmed the content about virtio-scsi. Please report any virtio-scsi issues in a new bug since I'm not convinced they are related to the issue you are having with lsilogic-dependendent VMs. Even if you think they are, I'd much rather treat them as separate and merge them later if necessary then try to triage both in the same bug. -dann
