Comment 2 for bug 1732481

So far I don't know how much impact does this configuration change have to qemu. Though it may be related to apparmor misconfigurations I received lately (eg. https://bugs.launchpad.net/nova/+bug/1728563).

Basically I would expect that when I for example attach volume to qemu instance, the apparmor profile will change and add path to volume allowed as read, write or lock, which didn't happen before and I was not able to attach volume in openstack.

I still need to test if changing qemu security driver has something to do with that and if it fixes my issues. I will report my results afterwards.