[vfio-users] Intel IGD VFIO passthrough success on i3-6100, but failed on i3-6100U

[Acewind]

I remeber your reply here:
https://www.mail-archive.com/vfio-users@redhat.com/msg03415.html
You said QEMU will fix the rom with correct device id automatically when
it's reading the rom directly from the device.

In today's env, the host is already booted in legacy mode. Do I still need
to dump the rom and fix the device id?

If I need, can I dump with these commands?
    echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
    cat /sys/devices/pci0000:00/0000:00:02.0/rom > vbios.dump
    echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom

Thanks!

Alex Williamson <alex.williamson at redhat.com> 于2018年10月12日周五 下午10:47写道：

> On Fri, 12 Oct 2018 17:41:42 +0800
> Acewind <acewind at gmail.com> wrote:
>
> > The two cpus all both SkyLake arch.
> >
> > I have successed to passthrough IGD device to Win7/Win10 on an  i3-6100
> > machine with Fedora 25.
> > I use legacy mode and set x-igd-gms=1 on qemu command line.
> >
> > When I work on another machine of i3-6100U with the same solution.
>
> You might try configuring the host BIOS to boot into legacy mode
> (non-UEFI) and use a live CD to get the legacy mode video BIOS from
> IGD.  You'll need to run rom-fixer on it to correct the checksum and
> device ID.  Then use the rom file option in libvirt xml to pass this
> image to the VM.  I've had this help before when the host system boots
> via UEFI natively.  Thanks,
>
> Alex
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/vfio-users/attachments/20181012/5b321805/attachment.htm>