Red Hat Bugzilla – Bug 984026
lxc container with networking hangs udevadm settle on the host
Last modified: 2016-04-26 12:27:59 EDT
+++ This bug was initially created as a clone of Bug #983685 +++
If I start a simple bash container with networking, udevadm settle proceeds to hang on the host. This affects other libvirt functions like storage pool listing. If I remove the <interface> XML, settle doesn't hang.
Any recommendations on getting more info is appreciated.
I have this container:
<target type='lxc' port='0'/>
Default network XML is:
<port start='1024' end='65535'/>
<bridge name='virbr0' stp='on' delay='0' />
<ip address='192.168.123.1' netmask='255.255.255.0'>
<tftp root='/var/lib/tftpboot' />
<range start='192.168.123.2' end='192.168.123.254' />
<bootp file='pxelinux.0' />
To test, dump the first XML to file, sudo virsh --connect lxc:/// define <vmxml>, sudo virsh --connect lxc:/// start bash, udevadm settle on host.udev
--- Additional comment from Daniel Berrange on 2013-07-12 10:17:20 BST ---
I've seen this before too, but never managed to get to the bottom of it. Will look again & ask systemd folks for opinions.
--- Additional comment from Daniel Berrange on 2013-07-12 14:52:04 BST ---
It's a pretty nasty kernel issue with network namespaces, or a non-trivial
problem to work around in userspace:
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Fixed in 212, see the fedora bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.