I looked into this a little more and believe this is a limitation of
libvirt and kvm interaction. kvm doesn't seem to have a way to specify
the image is readonly. The best option is to suppress the denied message
since it will happen every time and lead to confusion in normal use (and
debugging).
** Summary changed:
- libvirt via virt-manager tries to write to a readonly ISO image
+ libvirt tries to write to open a file with write permissions for a readonly
ISO image
** Summary changed:
- libvirt tries to write to open a file with write permissions for a readonly
ISO image
+ apparmor complains about write access to a readonly ISO image
** Changed in: libvirt (Ubuntu)
Status: New => Triaged
** Changed in: libvirt (Ubuntu)
Milestone: None => ubuntu-9.10
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) => Jamie Strandboge (jdstrand)
** Also affects: libvirt (Ubuntu Karmic)
Importance: Low
Assignee: Jamie Strandboge (jdstrand)
Status: Triaged
--
apparmor complains about write access to a readonly ISO image
https://bugs.launchpad.net/bugs/453335
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
