Re: [Lxc-users] Fwd: Container inside an ESX VM
Thanks, help is really appreciated. Cheers, Olivier On Sun, Apr 17, 2011 at 8:39 AM, Geordy Korte gko...@gmail.com wrote: Hi, Thought about it some more and i think it might be an advanced esx feature that restricts this. Basically a couple of adv features block spoofing and mac changes on a vhost. I will try to find the specific command you need to run on an esx host tomorrow, or maybee someone can google it. I am 100% sure that it's not a bug in either esx or lxc and no modifications are needed on the lxc side. Mvg Geordy Korte (Sent via iphone so shorter then normal) On 16 apr. 2011, at 23:51, Ulli Horlacher frams...@rus.uni-stuttgart.de wrote: 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: horlac...@rus.uni-stuttgart.de 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 Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] lxc-clone
On 04/06/2011 04:05 PM, Serge E. Hallyn wrote: Quoting Daniel Lezcano (daniel.lezc...@free.fr): What do you think is the best way to do this? We could allow the user to specify a 'firstboot' script, which gets copied into root directory of the container. Maybe boot the container when it's done, run /firstboot.sh, and shut down. Or just let that happen when the user first boots. We could use a /etc/init.d/lxc-firstboot script, but that will only work if the container's init system actually looks at sysvinit scripts. Obviously sysvinit and upstart do, and I must assume that systemd does. lxc-init I assume doesn't. Mmh, that's look a bit complicate for the user. I was thinking about something simpler like: grep -q lxc.utsname $lxc_path/$lxc_new/config if [ $? == 0 ]; then sed -e s/lxc.utsname/lxc.utsname=$hostname $lxc_path/$lxc_new/config else echo lxc.utsname = $hostname $lxc_path/$lxc_new/config fi and so for the rest of the configuration variables. Ok, yeah, that'll be necessary and independent of the distro. But I do think a firstboot option will be useful both for -clone and -create. It can be totally optional so as not to confuse those who don't want it. I am not sure to understand what is for the 'firstboot' option. Can you elaborate a bit ? -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Fwd: Container inside an ESX VM
So some more testing today. Here's what happens: When i have one container up with my host network restart trick, everything's fine, i can download gigas of data without problem. Starting a second one, redo the network trick to have network in this one either, everything looks ok. About 5minutes later interface get shut down and kernel panic... That's all for today :D On Mon, Apr 18, 2011 at 11:47 AM, Mauras Olivier oliver.mau...@gmail.comwrote: Thanks, help is really appreciated. Cheers, Olivier On Sun, Apr 17, 2011 at 8:39 AM, Geordy Korte gko...@gmail.com wrote: Hi, Thought about it some more and i think it might be an advanced esx feature that restricts this. Basically a couple of adv features block spoofing and mac changes on a vhost. I will try to find the specific command you need to run on an esx host tomorrow, or maybee someone can google it. I am 100% sure that it's not a bug in either esx or lxc and no modifications are needed on the lxc side. Mvg Geordy Korte (Sent via iphone so shorter then normal) On 16 apr. 2011, at 23:51, Ulli Horlacher frams...@rus.uni-stuttgart.de wrote: 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: horlac...@rus.uni-stuttgart.de 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 Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users -- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
