On 06/17/2010 06:49 PM, Nirmal Guhan wrote:
Hi,
Any reason why we require bridging in the host for lxc ? Am not able to
setup IP address for the container unless I configure bridge in the host.
You can use the macvlan but the container -- host communication won't
work.
Also couple of
Hello,
I'm working on a LXC plugin for collectd (A system statistics collection
daemon): http://collectd.org.
My goal is to get statistics on a container almost as if it was a real server.
I have started to focus on RAM and CPU usage.
I have carefully read the cgroups documentation in the
On Fri, Jun 18, 2010 at 9:39 AM, Daniel Lezcano daniel.lezc...@free.fr wrote:
On 06/17/2010 06:49 PM, Nirmal Guhan wrote:
Hi,
Any reason why we require bridging in the host for lxc ? Am not able to
setup IP address for the container unless I configure bridge in the host.
You can use the
Hi,
I gave a reboot command (accidently) from container. Although it did
not reboot the system, it made it less functional. All the vtys were
closed and could not open any new terminal. Had to reboot the system
to make it functional again.
Have any one seen such behavior ? This is with 2.6.32
I gave a reboot command (accidently) from container. Although it did
not reboot the system, it made it less functional. All the vtys were
closed and could not open any new terminal. Had to reboot the system
to make it functional again.
Have any one seen such behavior ? This is with 2.6.32
