Hey all,
I had this exact same error pop up for me recently, but the fix was
completely different.
Upon further investigation of /var/log/libvirt/qemu/Windows XP image
name, I saw that the KVM was attempting to mount a physical CDrom when
there was no CDROM in the CD tray. Because of that, it
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 150, in startup
self._backend.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 300, in
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 150, in startup
self._backend.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 300, in
This bug is fixed in Lucid. People who are still having problems should
file a new bug with 'ubuntu-bug libvirt'.
** Changed in: libvirt (Ubuntu Lucid)
Status: Confirmed = Fix Released
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You
Hey guys, I know this has been closed a while, but was still getting the error
when trying to start a VM in Lucid RC:
libvirtError: monitor socket did not show up.: Connection refused
When I updated my file and rebooted I'm now getting:
Unable to open connection to hypervisor URI
I am also seeing the same connection refused error as skogs. Should we
open a separate ticket about it?
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is
AppArmor should not be not causing this connection refused message
because skogs said there is nothing in the dmesg indicating a denial.
Indeed, skogs removal of 'audit deny /etc/apparmor.d/libvirt/** wxl,'
should not have done anything because the libvirtd profile disallows
this access regardless
I've been should on before, but I did remove my comment and everything
still works even after a system reboot. I withdraw my complaint. Shame
on me. Of course now I have no idea what originally caused it to not
work, but I've been trusting in FM for a long time.
--
[Lucid] Error starting
I don't suppose there is any explanation why I just upgraded to 10.04 and this
popped back up ehh?
Error reported in window:
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File
commented out the following line and fixed my issues.
audit deny /etc/apparmor.d/libvirt/** wxl,
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Just to chime in: I had this bug this morning (Apr 15) after I ran
upgraded my Lucid:
Error starting domain: could not remove profile for
'libvirt-55359786-ed36-5577-0d71-f252432b9388'
raceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
I also encountered this issue just now. It is caused by an update of the
apparmor profile:
--- /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper 2010-04-14
14:19:00.0 +0200
+++ /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper.dpkg-dist2010-04-15
08:17:39.0 +0200
@@ -3,6 +3,7
Since Ubuntu counts me too!! as people affected: ME TOO!!
Nothing more to add.
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in
Can people post the output of of 'dmesg' after they see this error.
Also, can you give the XML for the machine that is failing to start
(virsh dumpxml machine name')?
** Also affects: libvirt (Ubuntu Lucid)
Importance: Critical
Assignee: Jamie Strandboge (jdstrand)
Status: Fix
dmesg output:
[ 160.754633] device vnet0 entered promiscuous mode
[ 160.755215] br0: port 2(vnet0) entering learning state
[ 160.756086] device vnet1 entered promiscuous mode
[ 160.756580] br1: port 2(vnet1) entering learning state
[ 160.824741] br0: port 2(vnet0) entering disabled state
[
Traceback (most recent call last):
File /usr/share/virt-manager/virtManager/engine.py, line 588, in run_domain
vm.startup()
File /usr/share/virt-manager/virtManager/domain.py, line 150, in startup
self._backend.create()
File /usr/lib/python2.6/dist-packages/libvirt.py, line 300, in
Reverting /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper as described
above worked for me.
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
dmesg output:
[ 1341.500672] type=1503 audit(1271335124.806:17): operation=open pid=15949
parent=1779 profile=/usr/lib/libvirt/virt-aa-helper requested_mask=r::
denied_mask=r:: fsuid=0 ouid=0 name=/data/sas/vmimages/zimbra.img
[ 1341.500853] type=1503 audit(1271335124.806:18): operation=open
Can people seeing this issue comment out the following line in
/etc/apparmor.d/usr.lib.libvirt.virt-aa-helper:
#deny /dev/** mrwkl,
Then perform:
$ sudo apparmor_parser -r /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
Please report back if the machine starts (don't worry about denied
That worked for me, Jamie! :)
-RR
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
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
Yes, I can confirm this once I unload all my VM profiles. I had a hard
time confirming because they were already loaded and didn't unoload on
VM shutdown/destroy. The 'deny /dev/** mrwkl,' is much too zealous.
** Changed in: libvirt (Ubuntu Lucid)
Status: Incomplete = Confirmed
** Changed
I've the same problem since the latest updates to the kernel
(2.6.32-20-server - 2.6.32-21-server), some updates to
apparmor/profiles and libvirt.
Since some days I've 100% cpu load with 10.04 guest and host (4 cpus,
lvm2, virtio net and hd). So I can't use any guest.
--
[Lucid] Error starting
Martin, the 100% CPU load is a different issue (see bug #549428).
** Changed in: libvirt (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are
The fixed usr.lib.libvirt.virt-aa-helper from Jamie and a
apparmor_parser -r /etc/apparmor.d/usr.lib.libvirt.virt-aa-helper
helps and the guest is starting again.
The newest kernel, apparmor and libs fixed my problem with 100% load and
very slow guests.
--
[Lucid] Error starting domain: could
This bug was fixed in the package libvirt - 0.7.5-5ubuntu24
---
libvirt (0.7.5-5ubuntu24) lucid; urgency=low
* debian/apparmor/usr.lib.libvirt.virt-aa-helper: eek, the /dev change from
the last upload was a wee bit too aggressive. Revert that and allow access
to .img,
This bug still exists on karmic
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
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
That last message was intended for Chad. Chad, can you attach your dmesg
after seeing the failure?
** Package changed: virt-manager (Ubuntu) = libvirt (Ubuntu)
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Incomplete
** Tags added: apparmor
--
[Lucid] Error starting domain: could
Sure... attempts from two different VMs...
[ 1287.883490] type=1503 audit(1265396838.963:19): operation=profile_replace
pid=5756
[ 1287.896774] device vnet0 entered promiscuous mode
[ 1287.897141] br0: port 2(vnet0) entering forwarding state
[ 1287.930561] br0: port 2(vnet0) entering disabled
I see that in my logs too. Let me know if there's anything else you need
from me. Thanks for being so responsive.
--
[Lucid] Error starting domain: could not remove profile
https://bugs.launchpad.net/bugs/517714
You received this bug notification because you are a member of Ubuntu
Server Team,
Actually, this is not a profiling issue. The error from
/var/log/libvirt/qemu/log is:
libvir: Security Labeling error : error calling aa_change_profile()
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: libvirt (Ubuntu)
Assignee: (unassigned) = Jamie
I just encountered the same error. After reading the blog post at
http://penguindroppings.wordpress.com/2009/11/03/apparmor-svirt-security-driver-for-libvirt/
I tried to set
security_driver = none
in /etc/libvirt/quemu.conf but the problem still occurs. Can I somehow help
solving this problem?
As a workaround to this problem, disabling the apparmor profiles helped. I
disabled all profiles, but it might be a good idea to only disable the profiles
of libvirt. To disable all profiles you may use:
sudo aa-complain /etc/apparmor.d/*
More Information can be found at
flolle, please do not disable all of the profiles. This is not needed
and there are many profiles in place that are not causing the problem.
To workaround this, you can edit qemu.conf as suggested (and restart libvirtd),
or simply temporarily disable the apparmor profile until a reboot with:
$
This bug was fixed in the package libvirt - 0.7.5-5ubuntu6
---
libvirt (0.7.5-5ubuntu6) lucid; urgency=low
* debian/patches/9013-apparmor-dont-clear-caps.patch: Don't clear
capabilities when calling virt-aa-helper. When built with libcap-ng,
clearing caps makes
34 matches
Mail list logo
