On Wed, 2014-08-13 at 17:39 +0000, Anjali Kulkarni wrote: > Yes, but does this not go through the host? That is, the host's > eth0(management) has to be in this bridge?
No it does not. If you're using a NATed bridge, the hosts eth0 is NOT part of the bridge. > I want to be able to create > multiple such bridges, so I cannot add the eth0 of host to every such > bridge.. Then don't add eth0 to the bridge. You just create and empty bridge and go from there. > This works already, I want a "private" bridge between VM and container, > which does not go through the host. > Anjali > On 8/13/14 10:36 AM, "CDR" <[email protected]> wrote: > > >Do a real bridge on the host and use it on both the VM and the > >container. I do it all the time. > > > >On Wed, Aug 13, 2014 at 1:25 PM, Anjali Kulkarni <[email protected]> > >wrote: > >> Thanks - is there any way to do a private bridge between a VM and a > >> container, so that they can communicate? What's the use case of using > >> macvlan on a real nic? > >> > >> Anjali > >> > >> On 8/13/14 9:35 AM, "Serge Hallyn" <[email protected]> wrote: > >> > >>>You can't do macvlan on a bridge. It has to be done on an real > >>>physical nic. > >>> > >>>Quoting Anjali Kulkarni ([email protected]): > >>>> > >>>> Hi, > >>>> > >>>> We are trying to have a VM and a container ping each other via a > >>>>private > >>>> bridge (not going through host) via macvlan interface. A bridge, > >>>>lxcbr1 > >>>>is > >>>> already created and contains a link from VM, and we want to add > >>>>container > >>>> to it as well. > >>>> To do that, on adding the foll. config to a container, the error shown > >>>> below is seen, and tips about how to fix this issue? > >>>> > >>>> Config: > >>>> lxc.network.type = macvlan > >>>> lxc.network.macvlan.mode = bridge > >>>> lxc.network.flags = down > >>>> lxc.network.name = eth0 > >>>> lxc.network.link = lxcbr1 > >>>> lxc.network.ipv4 = 1.1.1.1/24 > >>>> > >>>> > >>>> Error seen: > >>>> lxc-start: failed to move 'lxcbr1' to the container : Invalid argument > >>>> lxc-start: failed to create the configured network > >>>> lxc-start: failed to spawn 'test' > >>>> lxc-start: The container failed to start. > >>>> lxc-start: Additional information can be obtained by setting the > >>>>--logfile > >>>> and --log-priority options. > >>>> > >>>> Thanks > >>>> Anjali > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> _______________________________________________ > >>>> lxc-users mailing list > >>>> [email protected] > >>>> http://lists.linuxcontainers.org/listinfo/lxc-users > >>>_______________________________________________ > >>>lxc-users mailing list > >>>[email protected] > >>>http://lists.linuxcontainers.org/listinfo/lxc-users > >> > >> _______________________________________________ > >> lxc-users mailing list > >> [email protected] > >> http://lists.linuxcontainers.org/listinfo/lxc-users > >_______________________________________________ > >lxc-users mailing list > >[email protected] > >http://lists.linuxcontainers.org/listinfo/lxc-users > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users > -- Michael H. Warfield (AI4NB) | (770) 978-7061 | [email protected] /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF | possible worlds. A pessimist is sure of it!
signature.asc
Description: This is a digitally signed message part
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
