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: [email protected] Universitaet Stuttgart Tel: ++49-711-685-65868 Allmandring 30 Fax: ++49-711-682357 70550 Stuttgart (Germany) WWW: http://www.rus.uni-stuttgart.de/ ------------------------------------------------------------------------------ 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. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Lxc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxc-users
