On Thu, Sep 21, 2023 at 10:43:50AM -0600, Alex Williamson wrote: > > With that code in place a legacy driver in the guest has the look and > > feel as if having a transitional device with legacy support for both its > > control and data path flows. > > Why do we need to enable a "legacy" driver in the guest? The very name > suggests there's an alternative driver that perhaps doesn't require > this I/O BAR. Why don't we just require the non-legacy driver in the > guest rather than increase our maintenance burden? Thanks, It was my reaction also. Apparently there is a big deployed base of people using old guest VMs with old drivers and they do not want to update their VMs. It is the same basic reason why qemu supports all those weird old machine types and HW emulations. The desire is to support these old devices so that old VMs can work unchanged. Jason
