On 06/15/2009 06:12 PM, Dor Laor wrote: >> It doesn't want to. As Mark said, libvirt just wants to be able to >> ensure >> a stable guest ABI, of which stable PCI addresses is one aspect. This >> does >> not imply libvirt wants to allocate the PCI addresses, just that it >> wants >> a way to keep them stable. All else being equal I'd rather libvirt >> wasn't >> in the PCI address allocation business. > > > It's not about what libvirt wants. It's about what will serve the end > user the most. > Apart for stable guest ABI, end users need to have the option to > control the slot for > their devices. Just like them have for physical machines. It's not > theoretical discussion, > limiting issues with shared irq is one real life example. > Another issue is enumeration. Guests will present their devices in the order they find them on the pci bus (of course enumeration is guest specific). So if I have 2 virtio controllers the only way I can distinguish between them is using their pci slots. -- error compiling committee.c: too many arguments to function _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
