Documenting the workarounds we have until this is solved properly are as following: - use virsh attach (hot-add) instead of adding it to the guest right away - If you happen to use the same USB port every time the IDs won't change and you can check what was blocked in dmesg and add just that to the guests (or if you need for more guests libvirt-qemu profile) apparmor profile - Open up USB more or less in general in libvirt-qemu profile (least recommended for security reasons)
It is yet unclear why: 1. it depends on hot-add vs initial device add (virt-aa-helper makes no difference on these two) 2. it works on some devices but not on others Please add in every case of this here that you have found with: 1. guest xml 2. lsusb 3. dmesg showing the blocker (Mine is the initial description with a flash drive) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686324 Title: usb hostdev passthrough generates the wrong apparmor rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1686324/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
