<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="blue" vlink="purple"> <div class="WordSection1"> I did not have success with adding the modules-load=vfio-pci arguments to the kernel line. Finally I tried a cron script that waits for 20 seconds after boot and then starts the guest. So autostart still isn’t working, but I have a workaround.<o:p></o:p> <o:p> </o:p> Thanks again,<o:p></o:p> Randy<o:p></o:p> <o:p> </o:p> Randall Pittman<o:p></o:p> Faculty Research Assistant | School of Civil and Construction Engineering | Oregon State University<o:p></o:p> Location: 006 Covell Hall | Mailing: 101 Kearney Hall | Corvallis, OR 97331-2132<o:p></o:p> Office: 541-737-2102 | Mobile: 541-286-7896<o:p></o:p> <o:p> </o:p> From: Colin Godsey [mailto:crgodsey@gmail.com] Sent: Thursday, March 31, 2016 2:19 PM To: Pittman, Randall; vfio-users@redhat.com Subject: Re: [vfio-users] PCI passthrough prevents autostart of guest<o:p></o:p> <o:p> </o:p> <div> You might have to try and early load the vfio module to head off any other drivers that may try to acquire the device. You should be able to do this with the rd.modules-load,modules-load kernel arguments.<o:p></o:p> <div> <o:p> </o:p> </div> <div> <a href="http://www.dsm.fordham.edu/cgi-bin/man-cgi.pl?topic=systemd-modules-load.service&ampsect=8">http://www.dsm.fordham.edu/cgi-bin/man-cgi.pl?topic=systemd-modules-load.service&ampsect=8</a><o:p></o:p> </div> </div> <o:p> </o:p> <div> <div> On Thu, Mar 31, 2016 at 2:55 PM Pittman, Randall <<a href="mailto:Randall.Pittman@oregonstate.edu">Randall.Pittman@oregonstate.edu</a>> wrote:<o:p></o:p> </div> <blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in"> <div> <div> Hi,<o:p></o:p> <o:p></o:p> I have a custom PCI data acquisition card for which I only have Windows XP drivers, so I’m running WinXP in a QEMU-KVM VM under CentOS 7. I have PCI passthrough working fine. (I added the PCI card to the VM with virt-manager) However, the VM will not autostart on boot of the host machine. I have the following output in /var/log/libvirt/qemu/win_xp.log:<o:p></o:p> <table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="border-collapse:collapse"> <tbody> <tr> <td valign="top" style="border:solid windowtext 1.0pt;padding:0in 5.4pt 0in 5.4pt"> 2016-03-29T18:29:26.191010Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: vfio: Error: Failed to setup INTx fd: Device or resource busy<o:p></o:p> 2016-03-29T18:29:26.289154Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: Device initialization failed.<o:p></o:p> 2016-03-29T18:29:26.289195Z qemu-kvm: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.0,addr=0x7: Device 'vfio-pci' could not be initialized<o:p></o:p> </td> </tr> </tbody> </table> <o:p></o:p> Again, this only happens at boot when the VM should be auto-starting. I can start it just fine manually with virsh or virt-manager. Perhaps the issue has to do with libvirtd starting too soon? N.b. I’m new to messing with init systems in general, systemd in particular.<o:p></o:p> <o:p></o:p> Any help would be greatly appreciated. I haven’t had any responses from the libvirt-users list, the CentOS forums, or my local university Linux mailing list.<o:p></o:p> <o:p></o:p> Thanks,<o:p></o:p> Randy<o:p></o:p> <o:p></o:p> Extended info:<o:p></o:p> · win_xp.xml file: <a href="http://pastebin.com/uBSbGDu6" target="_blank">http://pastebin.com/uBSbGDu6</a><o:p></o:p> · Software versions from yum:<o:p></o:p> o CentOS - 7.2.1511<o:p></o:p> o libvirt - 1.2.17-13.el7_2.3<o:p></o:p> o qemu - 2:2.0.0-1.el7.6<o:p></o:p> o qemu-kvm - 10:1.5.3-105.el7_2.3<o:p></o:p> · Hardware: <o:p></o:p> o CPU: Xeon E3-1231 v3, intel_iommu=on set in grub2<o:p></o:p> o lspci entry for the custom PCI card: 05:00.0 Unassigned class [ff00]: PLX Technology, Inc. PCI9054 32-bit 33MHz PCI <-> IOBus Bridge (rev 0b)<o:p></o:p> <o:p></o:p> <o:p></o:p> Randall Pittman<o:p></o:p> Faculty Research Assistant | School of Civil and Construction Engineering | Oregon State University<o:p></o:p> Location: 006 Covell Hall | Mailing: 101 Kearney Hall | Corvallis, OR 97331-2132<o:p></o:p> Office: 541-737-2102 | Mobile: 541-286-7896<o:p></o:p> <o:p></o:p> </div> </div> _______________________________________________ vfio-users mailing list <a href="mailto:vfio-users@redhat.com" target="_blank">vfio-users@redhat.com</a> <a href="https://www.redhat.com/mailman/listinfo/vfio-users" target="_blank">https://www.redhat.com/mailman/listinfo/vfio-users</a><o:p></o:p> </blockquote> </div> </div> </body> </html>