On Sat, May 14, 2011 at 4:06 PM, Serge Hallyn <serge.hal...@canonical.com>wrote:
> Hm, I just did this on natty
> (natty host, natty kvm VM, with a natty container inside that)
>
> and could actually not reproduce your problem. Just a normal bridge on
> the kvm VM:
>
> root@lxc-natty-amd64:~# brctl show
> bridge name bridge id STP enabled interfaces
> br0 8000.001636dd34bc no eth0
>
> And the lxc container was created with a minimal normal config:
>
> lxc.network.type=veth
> lxc.network.link=br0
> lxc.network.flags=up
>
>
Well, as I said it has to be something from the setup I do because I keep
having those problems even with laptop(natty)->kvm(natty)->host(natty)
I recorded this screencast that shows the issue:
http://www.screencast-o-matic.com/watch/cXhD2hbLM
Thanks
Arkaitz
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users
