On 11/16/2016 03:43 AM, Gerd Hoffmann wrote:
Hi,
I looked at "lspci" of a guest that has virtio-gpu directly connected to
pci-root, and found that it does show up as a legacy device in that
case, which I guess is what we want, right?
Let's ask the author of virtio-gpu: Gerd, what is your op
On Tue, 2016-11-15 at 11:15 -0500, Laine Stump wrote:
> I looked at "lspci" of a guest that has virtio-gpu directly connected to
> pci-root
pcie-root?
> and found that it does show up as a legacy device in that
> case, which I guess is what we want, right?
I tried with virtio-vga and it works as
On 11/15/2016 09:58 PM, Laine Stump wrote:
On 11/15/2016 12:44 PM, Alex Williamson wrote:
On Tue, 15 Nov 2016 13:21:21 +0100
Andrea Bolognani wrote:
On Thu, 2016-10-06 at 10:34 -0400, Laine Stump wrote:
+
+
+
I was initially baffled by this, because I expected it to
be ass
Hi,
> I looked at "lspci" of a guest that has virtio-gpu directly connected to
> pci-root, and found that it does show up as a legacy device in that
> case, which I guess is what we want, right?
>
> Let's ask the author of virtio-gpu: Gerd, what is your opinion - when
> using virtio-gpu as t
On 11/15/2016 12:44 PM, Alex Williamson wrote:
On Tue, 15 Nov 2016 13:21:21 +0100
Andrea Bolognani wrote:
On Thu, 2016-10-06 at 10:34 -0400, Laine Stump wrote:
+
+
+
I was initially baffled by this, because I expected it to
be assigned to one of the available pcie-root-por
On Tue, 15 Nov 2016 13:21:21 +0100
Andrea Bolognani wrote:
> On Thu, 2016-10-06 at 10:34 -0400, Laine Stump wrote:
> > > > +
> > > > +
> > > > + > > > function='0x0'/>
> > >
> > > I was initially baffled by this, because I expected it to
> > > be assigned to one of the availabl
On 11/15/2016 07:21 AM, Andrea Bolognani wrote:
On Thu, 2016-10-06 at 10:34 -0400, Laine Stump wrote:
+
+
+
I was initially baffled by this, because I expected it to
be assigned to one of the available pcie-root-ports just
like all the other virtio devices.
However, accord
On Thu, 2016-10-06 at 10:34 -0400, Laine Stump wrote:
> > > +
> > > +
> > > + > > function='0x0'/>
> >
> > I was initially baffled by this, because I expected it to
> > be assigned to one of the available pcie-root-ports just
> > like all the other virtio devices.
> >
> > However,
On 10/06/2016 10:13 AM, Andrea Bolognani wrote:
On Tue, 2016-09-20 at 15:14 -0400, Laine Stump wrote:
libvirt previously assigned nearly all devices to a "hotpluggable"
legacy PCI slot even on machines with a PCIe root bus (and even though
most such machines don't even support hotplug on legacy
On Tue, 2016-09-20 at 15:14 -0400, Laine Stump wrote:
> libvirt previously assigned nearly all devices to a "hotpluggable"
> legacy PCI slot even on machines with a PCIe root bus (and even though
> most such machines don't even support hotplug on legacy PCI slots!)
> Forcing all devices onto legacy
libvirt previously assigned nearly all devices to a "hotpluggable"
legacy PCI slot even on machines with a PCIe root bus (and even though
most such machines don't even support hotplug on legacy PCI slots!)
Forcing all devices onto legacy PCI slots means that the domain will
need a dmi-to-pci-bridge
11 matches
Mail list logo
