[systemd-devel] questions about systemd-nspawn

Jake Edge jake at lwn.net
Tue Feb 5 12:10:14 PST 2013

On Tue, 5 Feb 2013 20:43:58 +0100 Kay Sievers wrote:
> On Tue, Feb 5, 2013 at 8:34 PM, Jake Edge <jake at lwn.net> wrote:
> > Howdy Lennart and the systemd gang,
> >
> > Trying to play with systemd-nspawn on a Fedora 18 system using a
> > 3.8-rc5 kernel (if it matters) with audit turned off
> You should be able to use audit=0 on the kernel command line.

yeah, i built in 'audit=0' on the command line so i didn't have to
figure out how to convince grub2 to add that each time (or do it
manually) ...

> > [FAILED] Failed to start D-Bus System Message Bus.
> > See 'systemctl status dbus.service' for details.
> >          Starting D-Bus System Message Bus...
> It seems to boo fine here.

Interestingly, the bug you reference
(https://bugzilla.redhat.com/show_bug.cgi?id=893751#c3 ) mentions
exactly the behavior I see, but I can see in the kernel boot log that I
have 'audit=0' ... if I pass
--capability=cap_audit_write,cap_audit_control to nspawn, it all
works ... 

The same behavior occurs with --releasever=rawhide when I use yum to
install the files for the container ... at least for me ...

I'm starting to think there is something different with my kernel build
or (perhaps unlikely) a 3.8-rc5 issue ...

I certainly seem to have audit=0, from the log:

Feb  5 12:18:06 chukar kernel: [    0.000000] Kernel command line:
audit=0 BOOT_IMAGE=/vmlinuz-3.8.0-rc5ay ...


Feb  5 12:18:06 chukar kernel: [    0.000000] audit: disabled (until


Jake Edge - LWN - jake at lwn.net - http://lwn.net

More information about the systemd-devel mailing list