On Thu, Jan 03, 2013 at 04:13:52PM +0100, Ján Tomko wrote:
> On 12/26/12 02:00, liguang wrote:
> > @@ -1801,10 +1803,13 @@ qemuBuildDeviceAddressStr(virBufferPtr buf,
> > * When QEMU grows support for > 1 PCI domain, then pci.0 change
> > * to pciNN.0 where NN is the domain number
> > */
> > - if (qemuCapsGet(caps, QEMU_CAPS_PCI_MULTIBUS))
> > + if (info->type == VIR_DOMAIN_DEVICE_ADDRESS_TYPE_PCIBRIDGE) {
> > + virBufferAsprintf(buf, ",bus=pci-bridge%d", info->addr.pci.bus);
> > + } else if (qemuCapsGet(caps, QEMU_CAPS_PCI_MULTIBUS)) {
> > virBufferAsprintf(buf, ",bus=pci.0");
>
> Is there any way (or plan) to use more pci buses with QEMU other than
> with the pci bridges? If not, we could just name the bridges pci.%d. (If
> we index the bridges from 1).
That depends on the machine type you are using. The PC machine type only
has a single PCI bridge. IIRC, the q35 machine type has multiple bridges.
Either way I don't think this is a problem for libvirt. When we add PCI
bridge devices we should just use the same 'pci.%d' as Jan suggests.
If the machine type in question has 2 bridges by default, this simply
means the user adding bridges must start from bus=2.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list