Simon,
Can you provide the kern.log after you see this error? Can you also give
the exact steps to reproduce this problem?
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
starting
Well, I think I've tracked it down:
The VM can't be started and virsh shows the above mentioned error when the
qcow2 disk source file is located in /etc (at least when in /etc/libvirt/qemu
or /etc/network). So the following snipplet in the XML file triggers the error:
disk type='file'
I have no idea about the inner functionality of apparmor. I thus tried
to get the hosts running by
sudo /etc/init.d/apparmor stop
But this doesn't seem to help. Still the same error...
Any idea how to disable apparmor for kvm/libvirt?
--
starting second kvm guest created using
Well after restarting libvirt (sudo /etc/init.d/libvirt-bin restart),
too it now works...
--
starting second kvm guest created using ubuntu-vm-builder fails with 'could not
remove profile'
https://bugs.launchpad.net/bugs/530400
You received this bug notification because you are a member of
Starting apparmor again, and restarting libvirt brings back the error.
--
starting second kvm guest created using ubuntu-vm-builder fails with 'could not
remove profile'
https://bugs.launchpad.net/bugs/530400
You received this bug notification because you are a member of Ubuntu
Server Team,
