On Tue, Jul 08, 2025 at 04:59:37AM -0400, Andrea Bolognani wrote: > On Mon, Jul 07, 2025 at 04:45:30PM -0600, Jim Fehlig wrote: > > BTW, what do you think about a similar change for x86_64? I vaguely recall > > the choice of lsilogic for broader Windows support. We checked w2k8r2-w2k25 > > and win10, none of which contain an LSI Logic driver. virtio-scsi may be a > > better default for x86_64 as well. > > virtio-scsi is always a better default these days, and that's why > virt-manager uses it across the board. > > For libvirt itself, we are forced to be more mindful of historical > defaults, even when they're unfortunate. That's why we still use > rtl8139 as the default network interface, or indeed lsilogic as the > default SCSI controller. > > We have a bit more leeway on non-x86 platforms because the same long > history simply doesn't exist. Arm virt machines were introduced when > virtio was already a thing, and effectively they will all be using > virtio for everything, regardless of libvirt's defaults. > > That said, if even Windows is starting to leave devices behind, > perhaps the "maximum guest OS compatibility" part of the argument for > historical defaults is getting weaker and we're getting closer to a > point where we simply have no choice but change them...
Well lsilogic is still offering maximum guest OS compatibility, because for new OS mgmt tools have forever had support to explicitly pick virtio-scsi, and thus no modern guest OS should ever be relying on libvirt's built-in default. The defaults are most likely to be used in scenarios with legacy OS where libosinfo data isn't indicating the use of virtio-scsi. So from that POV I don't think we should change the libvirt defaults here. aarch/riscv are in a much simpler position given they have no need to support any legacy OS which lack virtio With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
