Quoting Derek Simkowiak (ubu...@cool-st.com): > I have the same 4-second bridge freeze when using LXC containers and > lxc-start or lxc-stop. (I am using a custom script to create my LXC > containers.) I saw the reference to this above: > > https://www.redhat.com/archives/libvir-list/2010-July/msg00450.html > > I changed my custom script from this: > > MACADDR="00:16:3e:"`head /dev/urandom | md5sum | sed -r > 's/^(.{6}).*$/\1/; s/([0-9a-f]{2})/\1:/g; s/:$//;'` > > ...to this: > > MACADDR="fe:16:3e:"`head /dev/urandom | md5sum | sed -r > 's/^(.{6}).*$/\1/; s/([0-9a-f]{2})/\1:/g; s/:$//;'` > > ...and now the freezing is gone. > > Since this is my own custom script, I'm not sure what package it would > belong to. Just be aware that this is a fundamental "bridge" issue and > not limited to libvirt, KVM. It shows up with LXC and probably any > other system where you add a new MAC.
Thanks for your comment. Please talk with upstream lxc about how it can use it. I'm certain it will be helpful. That it is a general bridge property is indeed known. The fix in this bug is, like your script, simply working around that fact. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/584048 Title: kvm images losing connectivity w/bridged network -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
