Hi, <Imagine a rant at my bad personal time allocation to fix this properly at some point>
Checking on 17.04 case now ... On 17.04 it even seems to work for me as I mentioned in comment #7 - never the less that seems to depend on static vs hot add/remove. @RussianNeuroMancer - could you share the following to find where we need to adapt the workaroudn steps for you: 1. the XML snippet describing the USB device 2. the lsusb output matching those <if using static add that is in the guest xml all the time> 3. dmesg while starting the guest (for apparmor denials) 4. after the guest started (or even failed to start) check the UUID (e.g. via virsh edit) and then fetch the generated apparmor file from /etc/apparmor.d/libvirt/libvirt-<uuid>.files <if you use hot add via virsh attach> 3. dmesg while hot attaching the device (for apparmor denials) 4. after the attach (even if it failed) check the UUID (e.g. via virsh edit) and then fetch the generated apparmor file from /etc/apparmor.d/libvirt/libvirt-<uuid>.files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1552241 Title: libvirt-bin apparmor settings for usb host device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1552241/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
