The kernel does not appear to be *entirely* broken for vfio. I figured out
that if I didn't pass a specific PCI card to my guest, the guest would
start. So VGA passthrough is still working; the device that breaks the
kernel (for me anyway) is a PCI USB adapter.
On Fri, Feb 23, 2018 at 7:32 PM, Brett Peckinpaugh <b...@erylflynn.com>
> So is the entire 4.15 kernel broken for vfio?
> On February 23, 2018 6:15:38 PM PST, Nick Sarnie <commendsar...@gmail.com>
>> On Fri, Feb 23, 2018 at 6:04 PM, Will Marler <w...@wmarler.com> wrote:
>>> I'm running Arch and updating recently has caused my VM to stop booting.
>>> Watching journalctl I see this when I try to start the VM:
>>> "Feb 23 15:04:07 haze kernel: BUG: unable to handle kernel NULL pointer
>>> dereference at 00000000000000a8
>>> Feb 23 15:04:07 haze kernel: IP: down_write+0x12/0x30
>>> and some more. Full pastebin is here: https://pastebin.com/8u70XLWJ
>>> This happens when I try to start my domain (called "Win10Full"). When it
>>> occurs, virsh locks up -- if I'm in virsh and do "list" it sits
>>> indefinitely. If I ctrl-C at this point, "End of file while reading data:
>>> Input/output error" gets written to the log, and my host cannot be rebooted
>>> without a physical power cycle.
>>> There is nothing that gets written to /var/log/libvirt/qemu/Win10Full.log.
>>> I'm not sure how to proceed; I figured this mailing list would be the first
>>> place to start. Any suggestions?
>>> Thanks in advance,
>>> vfio-users mailing list
>> This is a bug in 4.15. You can either revert to 4.14, or revert this
>> patch and recompile the kernel:
>> vfio-users mailing list
vfio-users mailing list