You are indeed correct that specifying the format of the disk image file
corrected the issue. However, this is also a fairly large regression
over previous functionality. Configurations that worked flawlessly
under lucid will now break under maverick. Additionally, the reason for
the breakage wi
Actually, it supports backing stores just fine in both Lucid and
Maverick (I use them all the time) for both storage pools and backed
qemu disks (I use them all the time) and the issue you are seeing is a
result of an upstream libvirt security fix, and not the AppArmor
security driver.
What change
This is still an issue in Maverick.
--
AppArmor security driver does not support backingstore
https://bugs.launchpad.net/bugs/470636
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
--
Ubuntu-server-bugs mailing list
Ub
libvirt 0.7.5-5ubuntu21 is accepted into lucid, but some of the
intermediate versions were bounced out of the queue for simplicity's
sake - so this didn't get autoclosed. Changelog entry:
libvirt (0.7.5-5ubuntu18) lucid; urgency=low
* handle SDL graphics (LP: #545426). This can be dropped in 0
Not respinning beta ISOs for this, so will accept immediately after
beta2.
** Changed in: libvirt (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-2 => ubuntu-10.04
--
AppArmor security driver does not support backingstore
https://bugs.launchpad.net/bugs/470636
You received this bug notification
Uploaded 0.7.5-5ubuntu18 which fixes this. Just needs to be approved.
** Changed in: libvirt (Ubuntu Lucid)
Status: In Progress => Fix Committed
** Changed in: libvirt (Ubuntu Lucid)
Milestone: None => ubuntu-10.04-beta-2
--
AppArmor security driver does not support backingstore
http
** Changed in: libvirt (Ubuntu Lucid)
Status: Triaged => In Progress
--
AppArmor security driver does not support backingstore
https://bugs.launchpad.net/bugs/470636
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
Marking karmic task as Won't Fix as this will likely be too intrusive to
fix in Karmic's libvirt.
** Changed in: libvirt (Ubuntu Karmic)
Status: Triaged => Won't Fix
--
AppArmor security driver does not support backingstore
https://bugs.launchpad.net/bugs/470636
You received this bug noti
Yeah, that could work, too. I was going with 'rw' in case one keeps ALL
the image files in one place, the base images AND the overlays. I, for
example, have /path/to/images_dir/masters for the base images, and
/path/to/images_dir for the overlays.
--
AppArmor security driver does not support back
As the base images should be readonly anyway, you can add
/path/to/images_dir/** r,
--
AppArmor security driver does not support backingstore
https://bugs.launchpad.net/bugs/470636
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt i
If you're going with option 2., you can simply add the following line to
/etc/apparmor.d/abstractions/libvirt-qemu file's end (after the HOME
stuff)
/path/to/images_dir/** rw,
Then you can place you images for every guest in that folder or
subfolders. Tested and working on Karmic.
Note that this
I looked into this quite a bit, and the problem is that libvirt is
unaware of the pristine cow/snapshot that the disk file is referencing.
All that is in the machine definition is the entry, which points
only to the snapshot/cow, not the underlying image. I can't (and won't)
fix this because the o
12 matches
Mail list logo
