On Wed, Aug 22, 2018 at 12:49:48PM -0300, Eduardo Habkost wrote: > > The thing that has really tipped my mind this way is that even > > if we provide new device models, mgmt apps will be loathe to > > actually use them because it will prevent live migration of > > those guests to hosts with older libvirt. > > This might be an issue for some apps, but is it going to happen > in practice? Don't they all need mechanisms to flip a switch and > enable features that require newer host software, already? That is true, but most features that get added to virt these days are things which are opt-in for specific use cases. eg when we added mdev support if a guest gets given an mdev VGPU it obviously won't be migratable to older libvirt lacking mdev support. The mitigation is that only $TINY % of guests will be using mdev, so the compat problem won't widely affect things. With the alternative virtio models we're discussing here, the idea is that they'd be used by default for all new guest deployments, so the impact will be felt on every guest. > > So my feeling is we should do the work to enable use of Q35 > > by default in mgmt apps, for guest OS where it is known to > > work correctly today. Every other OS should just stick with > > i440fx as we already know that works for them today and Q35 > > doesn't offer legacy OS compelling enough benefits to switch. > > I'd still prefer if libvirt provided a saner configuration > mechanism, and let libosinfo and management apps decide what > works best for them. > > If it helps, I can send QEMU patches to make > virtio-0.9/virtio-1.0-non-transitional/virtio-1.0-transitional > appear as different device types. libvirt would then be able to > check if the device type implements "pci-express-device" or > "conventional-pci-device", instead of adding device-specific > placement logic. I don't think it makes a big difference from pov of the libvirt impl, as its just the difference between "-device virtio-net,modern=off" and "-device virtio-net-0.9". It still has the same amount of extra work and complexity rippling out from libvirt to mgmt apps, to address a problem (make old RHEL6 use Q35 instad of i440fx) that shouldn't really need to exist. 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 :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
