------- Comment From heinz-werner_se...@de.ibm.com 2019-03-25 10:39 EDT------- Steps to reproduce the issue:
In order to reproduce the behavior, it is necessary to have a crypto adapter assigned to the hypervisor LPAR. The following link contains instructions on how to setup a vfio-ap matrix device. http://kvmonz.blogspot.com/2018/12/qemu-v31-released.html Running virsh nodedev-list before and after construction the matrix device should expose the issue. If libvirt bails out on the vfio-ap device, all devices that would be scanned subsequently will vanish from the returned list of devices. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818854 Title: [Ubuntu] vfio-ap: add subsystem to matrix device to avoid libudev failures Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- The vfio-ap driver will create a matrix device in sysfs without a subsystem link. This triggers failures in libudev that might also lead to libvirt errors (e.g. see https://www.redhat.com/archives/libvir-list/2019-February/msg00837.html) The proper fix is to add a subsystem link (e.g. by providing a dummy bus). A fix for that is upstream in master branch already for kernel 5.1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=36360658eb5a6cf04bb9f2704d1e4ce54037ec99 This need to be applied to Bionic, Cosmic and Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1818854/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
