------- Comment From <email address hidden> 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.
------- Comment From <email address hidden> 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.