Description of problem: When invoking 'virt-install --host-device ...' to pass through a LSI SAS2308 based controller, there is extensive output to /var/log/messages relating to the 'mpt2sas' module, indicating a kernel crash. Version-Release number of selected component (if applicable): 3.14.3-200.fc20 (kernel) 16.100.00.00 (mpt2sas) How reproducible: consistently Steps to Reproduce: 1. use 'sudo virsh nodedev-list --tree' to identify the controller device 2. use 'sudo virt-install --host-device <device-id> --location Fedora-20-x86_64-netinst.iso ...' to create and launch a new Fedora 20 guest VM Actual results: Extensive output to /var/log/messages relating to the 'mpt2sas' module, indicating a kernel crash. The system then automatically reboots. I have attached the relevant output from /var/log/messages Expected results: VM guest starts successfully. Additional info: - Have tried passing 'pci=nomsi' to the host kernel, result: network interface devices disappear from the host. - Have tried passing 'pci=nomsi' to the guest kernel using --extra-args, result: same kernel crash. - Have tried passing 'options mpt2sas msix_disable=1' via /etc/modprobe.d/mpt2sas.conf, and re-generating initrd using dracut, result: same kernel crash.
Created attachment 897351 [details] Relevant output from /var/log/messages
Interestingly, the problem goes away if I use the debug kernel (provided by the 'kernel-debug' package). What is the difference in the debug kernel that prevents the crash from occurring?
I found another (possibly more preferable) workaround, compared to using the debug kernel: the problem also goes away if I disable "Pass-through DMA Support" in the BIOS (listed under "Intel VT for Directed I/O" on the "Processor Configuration" screen, with an Intel S1200V3RPL server board). However, I have no idea of whether there is any performance impact or other undesirable effect when disabling this option in the BIOS?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.