hi, Mariano Absatz - gmail wrote (08 Jul 2016 17:33:32 GMT) : >> thanx for your help. As you suspected, AppArmor seems to be the problem >> (see log below). [...] > OK. I managed to find out, but your help was invaluable.
> According to > https://help.ubuntu.com/community/KVM/Managing#Apparmor_Modification > I added to my /etc/apparmor.d/abstractions/libvirt-qemu file the following: > /dev/bus/usb/*/[0-9]* rw, > But that wasn't enough. Reading the specific messages on the systemd > journal I had to add 2 more lines there: > /run/udev/data/c189:* rw, > /run/udev/data/+usb* rw, > and after restarting the apparmor service tails booted alright from the usb > drive. > I'm posting this in the hope that someone else can benefit from it and I'd > like to thank intrigeri again for his/her help guiding me. Thanks for sharing your solution! I'm not sure what we should do with this info though, since it's not clear to me that the default (upstream / Debian) AppArmor policy for libvirt should allow raw access to all USB devices. So I would suggest to check the available documentation (I would start in /usr/share/doc/libvirt-daemon-system/README.Debian) and find the best place to put that information, so that advanced users who are up to passing through bare metal USB devices to a VM can do it. And then we can point to that info from "Running Tails from a USB stick or SD card". I'm not going to track that, so anyone willing to do the work, please follow-up on the appropriate forums (Debian bug tracker, tails-dev@, whatever, but probably not here). Cheers, -- intrigeri _______________________________________________ tails-support mailing list [email protected] https://mailman.boum.org/listinfo/tails-support To unsubscribe from this list, send an empty email to [email protected].
