On Mon, Apr 1, 2013 at 7:34 PM, Jon <three1...@gmail.com> wrote: > Hello, > > I'm experiencing the same issues as described in a previous thread, > http://openvswitch.org/pipermail/discuss/2012-June/007459.html > > unfortunately, that thread kinda died without a resolution. > > I followed these instructions to setup ovs and kvm on the host, > >>> >>> http://blog.allanglesit.com/2012/10/linux-kvm-ubuntu-12-10-with-openvswitch/ > > however, I did not install the ovs-brcompat package. > > KVM works beautifully with ovs (though I'm having some trouble with > OpenNebula and ovs, but I have an issue open with them, > http://www.mail-archive.com/users@lists.opennebula.org/msg10021.html I only > bring it up because I think ovs is configured correctly as I am able to get > vms connected when using libvirt / virsh xml templates) > > My lxc config looks like this: (gateway is 55.55.55.65, 55.55.55.66 is my > host) > >>> lxc.utsname = mysandbox >>> lxc.network.type = veth >>> lxc.network.flags = up >>> lxc.network.mtu = 1500 >>> lxc.network.link = ovsbr0 >>> lxc.network.script.up=/etc/lxc/ovsup >>> # As appropiate (line only needed if you wish to dhcp later. To be >>> unique) >>> #lxc.network.hwaddr = 00:FF:08:5E:00:01 >>> # (Use 0.0.0.0 if you wish to dhcp later) >>> lxc.network.ipv4 = 55.55.55.67/28 >>> # could likely be whatever you want >>> lxc.network.name = eth0 >>> lxc.mount = /lxc/mysandbox/fstab >>> lxc.rootfs = /lxc/mysandbox/rootfs >>> lxc.tty = 2 > > When I attempt to start my container: > >>> lxc-start -l DEBUG -d --name mysandbox -f /lxc/mysandbox/config -o >>> lxc.log > > I get the following error log: > >>> lxc-start 1364869829.848 DEBUG lxc_conf - allocated pty >>> '/dev/pts/2' (4/5) >>> lxc-start 1364869829.848 DEBUG lxc_conf - allocated pty >>> '/dev/pts/3' (6/7) >>> lxc-start 1364869829.848 INFO lxc_conf - tty's configured >>> lxc-start 1364869829.848 DEBUG lxc_console - using '/dev/null' >>> as console >>> lxc-start 1364869829.848 DEBUG lxc_start - sigchild handler set >>> lxc-start 1364869829.848 INFO lxc_start - 'mysandbox' is >>> initialized >>> lxc-start 1364869829.871 DEBUG lxc_start - Not dropping >>> cap_sys_boot or watching utmp >>> >>> lxc-start 1364869829.873 DEBUG lxc_conf - mac address of host >>> interface 'vethMGqL8q' changed to private fe:01:2b:f5:ec:f5 >>> lxc-start 1364869829.873 ERROR lxc_conf - failed to attach >>> 'vethMGqL8q' to the bridge 'ovsbr0' : Operation not supported >>> lxc-start 1364869829.887 ERROR lxc_conf - failed to create >>> netdev >>> lxc-start 1364869829.887 ERROR lxc_start - failed to create the >>> network >>> lxc-start 1364869829.887 ERROR lxc_start - failed to spawn >>> 'mysandbox' >>> lxc-start 1364869829.887 DEBUG lxc_cgroup - get_init_cgroup: >>> found init cgroup for subsys (null) at / >>> >>> >>> lxc-start 1364869829.887 DEBUG lxc_cgroup - destroying >>> /sys/fs/cgroup/cpuset//lxc/mysandbox >>> >>> lxc-start 1364869829.887 WARN lxc_cgroup - failed to open >>> directory: No such file or directory >>> lxc-start 1364869829.887 ERROR lxc_cgroup - No such file or >>> directory - failed to remove cgroup '/sys/fs/cgroup/cpuset//lxc/mysandbox' > > I also experience the same symptoms as described by the original reporter: > >>> root@loki:~# brctl showmacs ovsbr0 >>> read of forward table failed: Operation not supported
This is a bridge command, so at the very least it will require brcompat. It's likely that LXC is also making direct bridge commands. You could try it with brcompat, however, that is deprecated and has already been removed from future releases. The best would be to update LXC to directly use native OVS commands. _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
