When I simply create a vm, an extra disk and some xml like
<disk type='block'>
<driver name='qemu'/>
<source dev='/tmp/x.img'/>
<target dev='vdc' bus='virtio'/>
</disk>
and do
virsh attach-device saucy /tmp/x.xml --live
then the vm definition gets the /tmp/x.img definition, and
/etc/apparmor.d/libvirt/libvirt-$uuid.files has /tmp/x.img rw.
Can someone with a saucy or trusty nova setup please set
log_level = 1
in /etc/libvirt/libvirtd.conf, (then do
stop libvirt-bin; rm /var/log/libvirt/libvirtd.log; start libvirt-bin)
and reproduce this and attach /var/log/libvirt/libvirtd.log to
this bug? I'd like to see which path this takes through libvirt
when done by nova.
** Changed in: libvirt (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259860
Title:
Apparmor doesn't allow volume to attach in 13.10 Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1259860/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
