Here's a full output of /proc/iomem after I try to boot a vm. http://pastebin.com/WVhpzWSc
I'm not sure how to interpret it exactly, but below the first occurrence of 0000:00:02.0, there's BOOTFB. I don't know how more to disable early framebuffers than I already have. And for a more full log of the vm startup: http://pastebin.com/hnRG2eDh I'm not sure what the deal is, but windows definitely gets an opportunity here to insert an error message. On Fri, Nov 11, 2016 at 10:06 AM, Alex Williamson < alex.william...@redhat.com> wrote: > On Fri, 11 Nov 2016 09:52:49 -0700 > Paul Handy <paul.d.ha...@gmail.com> wrote: > > > > As others have reported, I've gotten this message despite best efforts: > > Failed to mmap 0000:00:02.0 BAR 2. Performance may be slow > > Are there any clues in /proc/iomem as to what might be consuming > resources on the device? > > FWIW, there are reports that Skylake and Kabylake GTT support isn't > quite right, some people see multiple images on the screen until the > real Intel drivers take over. I don't have access to either of these > to debug myself. Thanks, > > Alex >
_______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
