Memory limitation does not work for me:
root@vms2:/lxc# uname -a
Linux vms2 2.6.32-31-server #61-Ubuntu SMP Fri Apr 8 19:44:42 UTC 2011 x86_64
GNU/Linux
root@vms2:/lxc# grep CONFIG_CGROUP_MEM_RES_CTLR
/boot/config-2.6.32-31-server
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
On 05/17/2011 08:34 AM, Ulli Horlacher wrote:
Memory limitation does not work for me:
root@vms2:/lxc# uname -a
Linux vms2 2.6.32-31-server #61-Ubuntu SMP Fri Apr 8 19:44:42 UTC 2011 x86_64
GNU/Linux
root@vms2:/lxc# grep CONFIG_CGROUP_MEM_RES_CTLR
/boot/config-2.6.32-31-server
On Tue, May 17, 2011 at 09:10, Daniel Lezcano daniel.lezc...@free.fr wrote:
On 05/17/2011 08:34 AM, Ulli Horlacher wrote:
root@flupp:~# clp
Command Line Perl with readline support, @ARGV and Specials. Type ? for
help.
(perl):: undef $/; open F,'/tmp/1GB.tmp' or die; $_=F; print length
Dear
I have a debian running in a container
the /cgroup/vps-1/memory.usage_in_bytes display
10784768
10784768 - 10Mb memory used.
I estimate that this value did not reflect a running debian system
Is it true ?
best regards
Unfortunately I haven't managed to get any further :(
I can still ping the LXC containers from other hosts on the network, and
they can ping each other, but I cannot ping them from the pxelinux host
machine.
Comparing the network config between the pxelinux host and a
non-pxelinux host I can see
On Tue 2011-05-17 (09:10), Daniel Lezcano wrote:
Why can a container process allocate more than 1 GB of memory if there is
512 MB limit?
When a process reaches the memory limit size then the container will
begin to swap. This is not really what we want as
Oh... no!
In order to
On 05/17/2011 12:11 PM, David Touzeau wrote:
Dear
I have a debian running in a container
the /cgroup/vps-1/memory.usage_in_bytes display
10784768
10784768 - 10Mb memory used.
I estimate that this value did not reflect a running debian system
Is it true ?
Assuming you are referring
On Tue 2011-05-17 (17:18), David Touzeau wrote:
the host is a Virtual Machine stored on ESXi 4.0
The container can ping the host, the host can ping the container.
Issue is others computers network. cannot ping the container and the
container cannot ping the network.
I have had the same
Hello David,
As you can see you only force the MAC adress _inside_ the container, on the
host the MAC for the veth is out of the bounds for ESX it doesn't seem to
like that - At least that's my guess cause i have not been able to make it
work correctly with this configuration.
First thing to
I tried this way either, but there's two blocking problems with that - At
least for me:
- Can't use this feature on 2.6.32 kernels
- Have to reboot to had a new interface to setup a new container - Yeah the
say you want to add up a 11th container ;)
Olivier
On Tue, May 17, 2011 at 5:36 PM, Ulli
On Tue 2011-05-17 (17:40), Mauras Olivier wrote:
I tried this way either, but there's two blocking problems with that - At
least for me:
- Can't use this feature on 2.6.32 kernels
I have installed 2.6.39 without problems.
- Have to reboot to had a new interface to setup a new container -
Hello,
you can try allow switching ethernet interface to
promiscuous mode in ESXi host configuration.
Best regards,
Miroslav.
Dne 17.5.2011 17:18, David Touzeau napsal(a):
Dear
According last discuss i have tried to change MAC address up to:
00:50:56:XX:YY:ZZ
Thread was here :
Le mardi 17 mai 2011 à 17:36 +0200, Ulli Horlacher a écrit :
On Tue 2011-05-17 (17:18), David Touzeau wrote:
the host is a Virtual Machine stored on ESXi 4.0
The container can ping the host, the host can ping the container.
Issue is others computers network. cannot ping the container
13 matches
Mail list logo