In the pure aa-helper tests that continues to work with all my usual minor tests and it fixes dac and dac+apparmor label issues.
But I seem to run into issues with doing full guests:
qemu-system-x86_64: -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-yakkety-sec-testfix/master-key.aes: Unable to read /var/lib/libvirt/qemu/domain-2-yakkety-sec-testfix/master-key.aes: Failed to open file '/var/lib/libvirt/qemu/domain-2-yakkety-sec-testfix/master-key.aes': Permission denie
That is due to an apparmor deny and might be that this was the issue that was tried to be fixed with the breaking change in libvirt?
I'll run more tests on it on my own.
But I'd really like to coordinate with the author of the former change what the test case was that made him create the patch.
I made an experimental fix available at https:/ /launchpad. net/~paelzer/ +archive/ ubuntu/ libvirt- bug-1633207
In the pure aa-helper tests that continues to work with all my usual minor tests and it fixes dac and dac+apparmor label issues. id=masterKey0, format= raw,file= /var/lib/ libvirt/ qemu/domain- 2-yakkety- sec-testfix/ master- key.aes: Unable to read /var/lib/ libvirt/ qemu/domain- 2-yakkety- sec-testfix/ master- key.aes: Failed to open file '/var/lib/ libvirt/ qemu/domain- 2-yakkety- sec-testfix/ master- key.aes' : Permission denie
But I seem to run into issues with doing full guests:
qemu-system-x86_64: -object secret,
That is due to an apparmor deny and might be that this was the issue that was tried to be fixed with the breaking change in libvirt?
I'll run more tests on it on my own.
But I'd really like to coordinate with the author of the former change what the test case was that made him create the patch.