[Lxc-users] Fwd: Container inside an ESX VM

[Geordy Korte]

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.

Mvg

Geordy Korte
(Sent via iphone so shorter then normal)


On 16 apr. 2011, at 15:55, Mauras Olivier <oliver.mauras at gmail.com> wrote:

> 
> 
> On Sat, Apr 16, 2011 at 3:45 PM, Serge Hallyn <serge.hallyn at canonical.com> wrote:
> > As you see in this example, before issuing the network restart, my veth MAC
> > was already higher than the eth0 MAC but the guest hadn't a working network
> > connection.
> 
> Thanks for the info.
> 
> > After restarting network on the host while the guest is still running, as
> > you can see my MACs haven't changed a bit but now the network inside the
> > guest is working correctly.
> >
> > Hope this helps to better understand the problem.
> 
> Heh, but not to understand the cause of the problem :)
> 
> I will see if I can reproduce this problem next week with vmware
> workstation.
> 
> -serge
>  
> I'll check next week if that's not a problem with interface loadbalancing  on the ESX vswitch side...
> ------------------------------------------------------------------------------
> 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
> Lxc-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lxc-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20110416/c606af79/attachment.html>