Hi, mine is a i5-4570. Yes, I did some extensive “testing” with the Skyrim mod Enderal and Path of Exile. My assumption, that the BOOTFB stuff is caused by the EFI firmware driver itself was wrong then. No idea how efifb or simplefb manage to grab that device without being compiled in.
The only method for not tainting the GPU ram according to Alex is the use of a serial console, which would require additional hardware (either a serial port, which is unlikely available nowadays or a usb to serial converter device and a display capable of reading the input. If you boot in text mode and have actual output, that would be a more likely cause for the BSOD. Do you have any vfio errors in kernel log (or systemd journal), when the BSOD occurs? The BOOTFB issue is just the last part for having an untainted GPU. I found the BOOTFB issue in a thread from November: https://www.redhat.com/archives/vfio-users/2016-November/msg00014.html Linking to the first post. You really should grep /proc/iomem on a normal startup for the word BOOTFB before attempting to fix that, because for me and the thread starter the symptoms were vfio errors in kernel log, while the VM showed a blank screen (even without Intel driver) and Alex had this working without requiring that memory freeing. The solution is linked in the last comment: https://lists.gnu.org/archive/html/qemu-devel/2016-07/msg02469.html It would require kernel sources and a Makefile like this: ifneq ($(KERNELRELEASE),) # kbuild part of makefile obj-m := forcefully-remove-bootfb.o else # normal makefile KDIR ?= /lib/modules/`uname -r`/build default: $(MAKE) -C $(KDIR) M=$$PWD endif Read the qemu post for a usage description. Best regards, Manuel > Ah, glad to know that yours is working. My CPU is i5-4430, which is > Haswell too. Did u try to run any 3D program or just test with the > Aero windows GUI? > Both my host and my guest is booted in non-efi mode. The host have > Fedora 25 server installed with non-efi mode, since I'm using > traditional partion (not GPT). Boot mode won't affect, right? > The "basic setting" I'v done include ignore msrs, enable intel nested, > blacklist i915 & intel hda, mod kernel parameter to let vfio handle > i915 and disable modeset. Host is booting in text mode. > I can boot the guest any times without restart the host. Normal usage > is fine include Windows own ScreenSavers. Only 3D program bring the > BSOD. > > BTW, please could u point me to the BOOTFB issue? Couln't find any > useful info. > > Regards, > Daimon > > On Friday, December 23, 2016 9:43 PM, Manuel Ullmann > <manuel.ullm...@posteo.de> wrote: > > Hm, > > I have a HD 4600 in my i5 Haswell. It works fine since the ignore_msrs > hint. How do you boot your host system? If it is booted in UEFI mode, > does /proc/iomem contain the word BOOTFB prefixed by your gpu pci > address (on any boot)? In other words, have you fixed the BOOTFB > allocation issue, which seems to occur, when the EFI driver grabs the > boot GPU? > I would assume, that it is in CSM mode, because I couldn’t > even boot without clearing the GPU ram. However it could possibly > intervene in such a host configuration. > > Best regards, > Manuel > > Daimon Wang <daimon_sw...@yahoo.com> writes: > >> Yes, msrs ignored already, or you can't even install the Intel > driver. >> Thank you, any way. >> Any other hints? >> >> Regards, >> Daimon >> >> On Thursday, December 22, 2016 10:03 PM, Alex Williamson >> <alex.william...@redhat.com> wrote: >> >> On Thu, 22 Dec 2016 10:30:34 +0000 (UTC) >> >> Daimon Wang <daimon_sw...@yahoo.com> wrote: >> >>> Hi, I'm trying IGD passthrough with both Intel HD 4000 and HD 4600. >> Everything is fine, the Win7_64 VM start successful with Intel > driver >> installed, and Aero is enabled. However when I run PCMark05 or any >> real 3D wallpaper (windows 3D bubble is fine), I got a BSOD with " >> SYSTEM_SERVICE_EXCEPTION" from (IGDKMD64.SYS(code 3B). Is this a > know >> issue or I'm missing any settings? (Since I got Aero enabled, most > of >> basic settings should be ok) >> >> Add: >> >> options kvm ignore_msrs=1 >> >> to a file in /etc/modprobe.conf.d/ >> >> Thanks, >> >> Alex > >> >> >> _______________________________________________ >> vfio-users mailing list >> vfio-users@redhat.com >> https://www.redhat.com/mailman/listinfo/vfio-users > > > _______________________________________________ > vfio-users mailing list > vfio-users@redhat.com > https://www.redhat.com/mailman/listinfo/vfio-users _______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
