On Mon, 19 Nov 2018 19:32:32 -0200 Eduardo Habkost <ehabk...@redhat.com> wrote:
> However, I wish this kind of usability magic didn't automatically > imposed us the burden of keeping guest ABI compatibility too. > Keeping ABI compatibility on the machine-friendly device types and > interfaces is already hard enough. Hm, what are you thinking about here? We can fence off new features in the hw compat section (and we already do so today), so the remaining compat woe is what you are addressing with this patch set, isn't it? > > We already have aliases that automatically select a virtio device > type at qdev-monitor.c:qdev_alias_table[], and I don't know if > they are supposed to keep a stable guest ABI. As the comment there states, it was a bad idea... when you are using the alias, you can't pass any properties that are unique to the transport anyway. Hopefully the compat code dealt with the disable-modern for old machine types correctly in this case; but I don't think that helps for the bus dilemma. I'm not sure we want to worry about the aliases too much; it might even be a good idea to deprecate them. -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
