saucy armhf container does not start

[Jani Monoses]

Creating an armhf container on an amd64 host

$sudo lxc-create -n saucy-armhf -t ubuntu -- -a armhf -r saucy

$sudo lxc-start -n saucy-armhf

<4>init: ureadahead main process (6) terminated with status 5
<4>init: udev-fallback-graphics main process (68) terminated with status 1
<4>init: console-font main process (91) terminated with status 1
<4>init: setvtrgb main process (110) terminated with status 1
<4>init: console-setup main process (163) terminated with status 1
<4>init: udev main process (184) terminated with status 3
<4>init: udev main process ended, respawning
<4>init: rsyslog main process (226) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (248) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (273) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (283) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (293) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (303) killed by ABRT signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (313) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (323) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (333) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (343) killed by SEGV signal
<4>init: rsyslog main process ended, respawning
<4>init: rsyslog main process (353) killed by ABRT signal
<4>init: rsyslog respawning too fast, stopped

[Serge Hallyn (serge-hallyn)]

Thanks for reporting this bug. The rsyslog failure however is a bug in qemu-arm-static rather than in lxc.

Note that while the rsyslog respawns are filling up your console, the container should still be running. You should be able to log in on console (I can), and you can also start the container in the background and attach to a different console to avoid the messages. Lastly, you can change /etc/init/rsyslog.conf to add 'manual' on a line by itself to prevent rsyslog from starting.

[Jani Monoses (jani)]

I could see the container was running but lxc-console yielded only this:

Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself

Adding manual to rsyslog.conf results in a quieter start but still I cannot log on.

[Serge Hallyn (serge-hallyn)]

Fixed by Stéphane in upstream git.