If anyone is curious about this, the cause turned out to be related to
the way bridging works and how AWS deals with arp table updates. The
underlying problem is described here:
http://backreference.org/2010/07/28/linux-bridge-mac-addresses-and-dynamic-ports/
The solution was to add the line
I have hit a problem running libvirt based containers in a CentOS 7
based host, with the extra wrinkle that my host is an EC2 instance in
AWS. Ultimately everything works as advertised, and I can launch
instances that host multiple libvirt lxc containers without problems,
with one caveat: About
