[lxc-devel] Starting/Stopping container causes host instability - FC15 host, Centos 5.6 guest

Jonathan Essex jonessex at iquality.co.uk
Wed Aug 3 14:15:47 UTC 2011


I've installed LXC from GIT on a vanilla FC15 installation. I've not
explicitly mounted cgroup because the distro seems to be doing it
automagically and (as far as I understand it) the recent patches should
mean this works.

I've then followed the instructions here:

http://www.emanuelis.eu/2010/05/28/how-to-create-a-lxc-centos-template/

To create a centos 5.6 container. (I turned the mingettys back on in the
container inittab so that lxc-console works. Also the root fs is a loop
device which needed some fiddling to make it work)

To my great surprise and pleasure the container starts and stops OK.

However, once I have started and stopped a container on my host, the
host will no longer shut down cleanly. (I've reproduced this several
times).

Wondering if this could be some kind of bad interaction with systemd.
The host log section below shows me stopping the container and then
trying to log out of the gnome desktop on the host... there's a segfault
and other badness which happens only if I've started/stopped a
container.

Any pointers much appreciated...

Aug  3 07:21:38 pad-je4 dbus-daemon: [system] Activating service
name='org.freedesktop.PackageKit' (using servicehelper)
Aug  3 07:21:39 pad-je4 abrt[2653]: Unrecognized variable 'DumpLocation'
in '/etc/abrt/abrt.conf'
Aug  3 07:21:39 pad-je4 abrt[2653]: abrt daemon is not running. If it
crashed, /proc/sys/kernel/core_pattern contains a stale value, cons
ider resetting it to 'core'
Aug  3 07:21:39 pad-je4 dbus-daemon: [system] Activated service
'org.freedesktop.PackageKit' failed:
Process /lib64/dbus-1/dbus-daemon-la
unch-helper received signal 6
Aug  3 07:25:38 pad-je4 systemd-cgroups-agent[2753]: Failed to get D-Bus
connection: Failed to connect to socket /org/freedesktop/systemd
1/private: Connection refused
Aug  3 07:25:39 pad-je4 vmnetBridge: Removing interface veth6Gquyb
index:8
Aug  3 07:25:39 pad-je4 avahi-daemon[810]: Withdrawing address record
for fe80::742a:24ff:fe5a:4493 on veth6Gquyb.
Aug  3 07:25:39 pad-je4 kernel: [  605.454272] br0: port 1(veth6Gquyb)
entering forwarding state
Aug  3 07:25:39 pad-je4 kernel: [  605.464977] br0: port 1(veth6Gquyb)
entering disabled state
Aug  3 07:25:39 pad-je4 vmnetBridge: RTM_DELLINK: name:veth6Gquyb
index:8 flags:0x00001102
Aug  3 07:25:39 pad-je4 vmnetBridge: RTM_DELLINK: name:veth6Gquyb
index:8 flags:0x00001102
Aug  3 07:25:39 pad-je4 avahi-daemon[810]: Withdrawing workstation
service for veth6Gquyb.
Aug  3 07:26:06 pad-je4 abrt[2793]: Unrecognized variable 'DumpLocation'
in '/etc/abrt/abrt.conf'
Aug  3 07:26:06 pad-je4 abrt[2793]: abrt daemon is not running. If it
crashed, /proc/sys/kernel/core_pattern contains a stale value, cons
ider resetting it to 'core'
Aug  3 07:26:06 pad-je4 kernel: [  632.694445] at-spi-bus-laun[1688]:
segfault at 968 ip 000000337ae25321 sp 00007fffd8904970 error 4 in 
libX11.so.6.3.0[337ae00000+139000]
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplayAccessFile:
Unable to remove X11 authority database '/var/run/gdm/auth-for-j
onessex-pBqDJV/database': No such file or directory
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplayAccessFile:
Unable to remove X11 authority directory '/var/run/gdm/auth-for-
jonessex-pBqDJV': No such file or directory
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplayAccessFile:
Unable to remove X11 authority database '/var/run/gdm/auth-for-g
dm-2oApoq/database': No such file or directory
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplayAccessFile:
Unable to remove X11 authority directory '/var/run/gdm/auth-for-
gdm-2oApoq': No such file or directory
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplay: display
lasted 0.004500 seconds
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplay: display
lasted 0.005017 seconds
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplay: display
lasted 0.005413 seconds
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplay: display
lasted 0.005357 seconds
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplay: display
lasted 0.005393 seconds
Aug  3 07:26:06 pad-je4 gdm-binary[1273]: WARNING: GdmDisplay: display
lasted 0.005263 seconds











More information about the lxc-devel mailing list