<html><head></head><body>Would using macvlan bridge mode the solution?<br>
Didn't find a way to make it work...<br><br><div class="gmail_quote">Ulli Horlacher <framstag@rus.uni-stuttgart.de> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div style="white-space: pre-wrap; word-wrap:break-word; ">On Sat 2011-04-16 (22:24), Geordy Korte wrote:
> Due to the architecter of esx it will only permit 1 mac per vswitch port.
> If they would allow more then security would be comprimised. Solution
> would be to have each lxc bound to a vnic.
I have had the same problem with lxc on ESX last week. I also thought using separate vnics for each container would be a solution, but lxc has a bug not giving back the interface original name to the host: eg, eth1 becomes dev3 and you cannot rename it back.
The result of this bug is: you can start a container only once, then you have to reboot the host. This is a complete show stopper.
--
Ullrich Horlacher Server- und Arbeitsplatzsysteme
Rechenzentrum E-Mail: horlacher@rus.uni-stuttgart.de
Universitaet Stuttgart Tel: ++49-711-685-65868
Allmandring 30 Fax: ++49-711-682357
70550 Stuttgart (Germany) WWW: <a href="http://www.rus.uni-stuttgart.de">http://www.rus.uni-stuttgart.de</a>/<hr />Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. <a href="http://p.sf.net/sfu/vmware-sfdev2dev">http://p.sf.net/sfu/vmware-sfdev2dev</a><hr />Lxc-users mailing list
Lxc-users@lists.sourceforge.net
<a href="https://lists.sourceforge.net/lists/listinfo/lxc-users">https://lists.sourceforge.net/lists/listinfo/lxc-users</a>
</div></blockquote></div></body></html>