[vfio-users] Not binding GPU to vfio-pci

[Nick Sarnie]

Hi Alex,

Yeah it seems you're right, the qemu command has "-device
vfio-pci,host=01:00.0,id=hostdev2,bus=pci.0,addr=0x2", so it seems it is
using vfio-pci.Thanks for the information.

One more quick question: I'm using SeaBIOS for my VM. My GPU doesn't
support UEFI Secure/Fast booting. Can I use a GPU like this with OVMF and
more importantly, is there any performance difference using OVMF over
SeaBios? Thanks alot,
sarnex

On Sun, Feb 21, 2016 at 11:36 AM, Alex Williamson <
alex.williamson at redhat.com> wrote:

> On Sun, Feb 21, 2016 at 9:06 AM, Nick Sarnie <commendsarnex at gmail.com>
> wrote:
>
>> Sorry, I'm not sure if I'm using legacy device assignment. My script is
>> stop xdm, echo "0000:01:00.0" > /sys/bus/pci/drivers/radeon/unbind echo
>> "0000:01:00.1" > /sys/bus/pci/drivers/radeon/unbind and then start xdm. I
>> use virt-manager with libvirt, and I added the gpu to the VM with PCI Host
>> Device under Add Hardware. Is this what you're talking about?
>>
>
> Somehow I doubt that both function 0 and 1 are bound to the radeon driver,
> but if you're not crafting your own QEMU command line or specifying a
> driver for the hostdev entries in your XML, then you're probably using
> vfio.  You can verify by looking at the libvirt log for the VM
> (/var/log/libvirt/qemu/$domain.log) for either vfio-pci or pci-assign
> devices.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20160221/31c80921/attachment.htm>