Marking this bug invalid as we needed more information to act on.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
Sven, what version of libvirt and Ubuntu are you using? Can you attach
the output of 'virsh dumpxml your problem domain'? Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/607466
Hi Jamie,
I ran into exactly the same problem. My syslog output:
Aug 28 18:51:18 facitserver kernel: [ 2492.386304] device vnet0 entered
promiscuous mode
Aug 28 18:51:18 facitserver kernel: [ 2492.387292] virbr0: topology change
detected, propagating
Aug 28 18:51:18 facitserver kernel: [
libvirt-bin=0.7.5-5ubuntu27
qemu-kvm=0.12.3+noroms-0ubuntu9.2
r...@iadvirt02:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.1 LTS
Release:10.04
Codename: lucid
r...@iadvirt02:~# uname -a
Linux iadvirt02 2.6.32-24-generic
Actually, it does looks like an apparmor problem. Putting Apparmor in
complain mode allows the domain to start, returning it to enforce brings
back the original state.
r...@iadvirt02:~# aa-complain /etc/apparmor.d/usr.sbin.libvirtd
Setting /etc/apparmor.d/usr.sbin.libvirtd to complain mode.
I'm not sure how this state gets created but:
r...@iadvirt02:/etc/apparmor.d/libvirt# ls -l
total 8
-rw-r--r-- 1 root root 265 2010-07-15 19:44
libvirt-177bb534-7d9c-91ad-e6bf-89cd76d1e1bb
-rw-r--r-- 1 root root 164 2010-04-22 16:57 TEMPLATE
r...@iadvirt02:/etc/apparmor.d/libvirt# virsh start
Could you attach the xml profile of the failing guest (iadoptdc02)?
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Medium
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
libvirt error starting domin: could not remove profile for
Yes, although it's working at the moment.
domain type='kvm'
nameiadoptdc02/name
uuid177bb534-7d9c-91ad-e6bf-89cd76d1e1bb/uuid
memory1048576/memory
currentMemory1048576/currentMemory
vcpu2/vcpu
os
type arch='x86_64' machine='pc-0.12'hvm/type
boot dev='hd'/
/os
features
1) stopped libvirt via the libvirt-bin init script
2) started 'libvirtd -v' manually hoping to see some debugging output
3) started the guest okay.
4) destroyed the guest
5) canceled the manual libvirt
6) started libvirt-bin again with the init script
7) started the guest okay.
Note that AppArmor
