tag:blogger.com,1999:blog-8694303781453133223.post5837617849491939338..comments2023-12-12T08:07:13.883-07:00Comments on VFIO tips and tricks: Intel Graphics assignmentAlex Williamsonhttp://www.blogger.com/profile/02071923591707250496noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-8694303781453133223.post-79540141287749267262016-08-02T10:30:34.815-06:002016-08-02T10:30:34.815-06:00If you experience problems with BSODs in Windows, ...If you experience problems with BSODs in Windows, try enabling the kvm module option ignore_msrs. The risk of this is that unknown/unsupported MSRs will return 0, which may not always be the correct return value and may lead to other issues. The Intel graphics drivers are known to need this for now though.Alex Williamsonhttps://www.blogger.com/profile/02071923591707250496noreply@blogger.comtag:blogger.com,1999:blog-8694303781453133223.post-50905862855703990692016-07-21T13:46:31.438-06:002016-07-21T13:46:31.438-06:00Bingo! Thank you very much sir! I've just chan...Bingo! Thank you very much sir! I've just changed to the new SeaBIOS and it all works now. <br /><br />I've also got it working by blacklisting only i915 in /etc/modprobe.d/blacklist.conf so I don't have to execute 'virsh nodedev-detach pci_0000_00_02_0' after boot.<br /><br /><br />Stuff In Generalhttps://www.blogger.com/profile/04406966851045338936noreply@blogger.comtag:blogger.com,1999:blog-8694303781453133223.post-54120784821224966162016-07-21T13:31:30.681-06:002016-07-21T13:31:30.681-06:00You're using /home/user/vfio-bios/bios.bin for...You're using /home/user/vfio-bios/bios.bin for your BIOS and /usr/local/qemu-2.7.0-git-20072106/bin/qemu-system-x86_64 for the emulator, but qemu.git has the correct bios in it, so why aren't you using /usr/local/qemu-2.7.0-git-20072106/share/qemu/bios.bin for the BIOS? Where does vfio-bios come from? Are there any error messages in /var/log/libvirt/qemu/arch-gns3-2016-idg.log? I don't spot any other issues, but using the correct BIOS is critical and there was churn on that during development, so anything other than the final bits that went upstream won't work.Alex Williamsonhttps://www.blogger.com/profile/02071923591707250496noreply@blogger.comtag:blogger.com,1999:blog-8694303781453133223.post-29991210060912894452016-07-21T13:21:56.357-06:002016-07-21T13:21:56.357-06:00Here's the XML : http://pastebin.com/mLwrK4Bw
...Here's the XML : http://pastebin.com/mLwrK4Bw<br /><br />The processor is an i7-4770s (Haswell)Stuff In Generalhttps://www.blogger.com/profile/04406966851045338936noreply@blogger.comtag:blogger.com,1999:blog-8694303781453133223.post-12128046464427709092016-07-21T12:42:55.456-06:002016-07-21T12:42:55.456-06:00Can we see your guest XML/command line? What'...Can we see your guest XML/command line? What's the processor version?Alex Williamsonhttps://www.blogger.com/profile/02071923591707250496noreply@blogger.comtag:blogger.com,1999:blog-8694303781453133223.post-85005944275609131252016-07-21T12:38:00.596-06:002016-07-21T12:38:00.596-06:00I can see a difference now after letting i915 rab ...I can see a difference now after letting i915 rab the IGD and running 'virsh nodedev-detach pci_0000_00_02_0' as the console output to screen disappears. However the guest still fails to boot with no sign of any output on the screen:<br /><br />Here's the pastebin to the outputs after running 'virsh nodedev-detach pci_0000_00_02_0' <br /><br />http://pastebin.com/7WFFpG1TStuff In Generalhttps://www.blogger.com/profile/04406966851045338936noreply@blogger.comtag:blogger.com,1999:blog-8694303781453133223.post-74813653816844737382016-07-20T14:26:17.800-06:002016-07-20T14:26:17.800-06:00Can you pastebin /proc/iomem, /proc/ioport, and &#...Can you pastebin /proc/iomem, /proc/ioport, and 'lspci -vvvs 00:02.0', you'll need sudo for all of these on recent kernels. dmesg may also be useful. Clearly some console driver is still attaching to IGD. You might also find that you have more success letting i915 grab IGD, unbinding and preventing future binding. Generally the problems I see with i915 are re-binding after use by vfio-pci. 'virsh nodedev-detach pci_0000_00_02_0' at boot should do this.Alex Williamsonhttps://www.blogger.com/profile/02071923591707250496noreply@blogger.comtag:blogger.com,1999:blog-8694303781453133223.post-37599567523992927072016-07-20T14:12:55.975-06:002016-07-20T14:12:55.975-06:00Nice update Alex. I have this a quick go but could...Nice update Alex. I have this a quick go but couldn't get anywhere with it.<br /><br />I'm running Linux 4.7.0-rc7 and the very latest qemu-git. I blacklisted i915, and some other modules after troubleshooting by inserting the following in to /etc/modprobe.d/blacklist.conf:<br /><br />blacklist snd_hda_intel<br />blacklist i915<br />blacklist drm<br />blacklist drm_kms_helper<br />blacklist i2c_algo_bit<br />install snd_hda_intel /bin/false<br />install i915 /bin/false<br /><br />I also added video=vesafb:off,efifb:off to my kernel boot parameters. I can see that 00:02.0 has no kernel module in use when the system boots however I still get a console output on the screen. When I start the guest the console disappears and I see the below in dmesg but the guest never starts and I get no output on the screen:<br /><br />[ 67.980294] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem<br />[ 68.025793] br0: port 3(tap11) entered blocking state<br />[ 68.025796] br0: port 3(tap11) entered disabled state<br />[ 68.025854] device tap11 entered promiscuous mode<br />[ 68.052476] br0: port 3(tap11) entered blocking state<br />[ 68.052479] br0: port 3(tap11) entered forwarding state<br />[ 69.158471] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=io+mem:owns=none<br />[ 69.158473] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem<br />[ 78.675389] br0: port 3(tap11) entered disabled state<br />[ 78.676919] device tap11 left promiscuous mode<br />[ 78.676922] br0: port 3(tap11) entered disabled state<br />[ 78.912853] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem<br /><br /><br /><br />Stuff In Generalhttps://www.blogger.com/profile/04406966851045338936noreply@blogger.com