Comment 0 for bug 1307436

Revision history for this message
Daniel Gollub (d-gollub) wrote :

With Ubuntu 12.04 Precise and Cloudarchive Icehouse libvirt 1.2.2-0ubuntu11~cloud0 is not able to spawn a VM instance due to incompatible apparmor profile with apparmor 2.8.0 (precise's version):

2014-04-11 10:27:10.997+0000: 8616: error : virCommandWait:2399 : internal error: Child process (/usr/lib/libvirt/virt-aa-helper -p 0 -c -u libvirt-d18f1dff-e275-4fcc-b712-2caf530aed74) unexpected exit status 1: virt-aa-helper: error: apparmor_parser exited with error

Also starting apparmor with 1.2.2-0ubuntu11~cloud0 results in a apparmor_parser error:

root@compute1:~# /etc/init.d/apparmor start
 * Starting AppArmor profiles
AppArmor parser error for /etc/apparmor.d/usr.sbin.libvirtd in /etc/apparmor.d/usr.sbin.libvirtd at line 37: syntax error, unexpected TOK_CONDID, expecting TOK_MODE

When OpenStack/Nova/libvirt tries to spawn an instance it fails due to following apparmor_parser issue:

/etc/apparmor.d/libvirt/libvirt-3138433d-a124-40dd-9630-68a9e227b0bd
in /etc/apparmor.d/abstractions/libvirt-qemu at line 143: syntax error, unexpected TOK_OPENPAREN, expecting TOK_MODE

New offending profile entries for apparmor 2.8.0 seems to be:

/etc/apparmor.d/usr.sbin.libvirtd:
  dbus bus=system,
  signal,
  ptrace,

/etc/apparmor.d/abstractions/libvirt-qemu:
  signal (receive) peer=/usr/sbin/libvirtd,
  ptrace (tracedby) peer=/usr/sbin/libvirtd,

Reverting those entries allows again to spawn a VM instance with OpenStack Icehouse RC2 from Cloudarchive-Ichouse on Ubuntu 12.04 Precise.