Hii all
I am using lxc for creating containers.
But when i create lxc container using "lxc-create -n abc" it creates a abc
container and when i do lxc-info -n abc its show "abc is stopped" and when i
perform "lxc-start -n abc [-f conf file ]" the terminal hangs and if do
"lxc-execute -n abc [-f
first thought put it in lxc-create
then again, conversion is needed too hence i also want an lxc-convert
i am coming from a qemu background
so qemu-img does create and convert
so optimum is to see an lxc-convert and have that function also
available as part of lxc-create
On Fri, Jul 1, 2011 at 8:
It seems you didn't bootstrap any distribution. Please see
http://blog.foaa.de/2010/05/lxc-on-debian-squeeze/ , note especially
the use of debootstrap
On Wed, Aug 24, 2011 at 5:30 PM, nishant mungse wrote:
> Hii all
> I am using lxc for creating containers.
> But when i create lxc container usi
On Fri 2011-07-01 (12:31), Serge E. Hallyn wrote:
> so lxc-clone will create a snapshot-based clone of an lvm-backed
> container in about a second.
My "lxc" script (*) can do this in 2 seconds, without bothering LVM:
root@vms2:/lxc# lxc
usage: lxc option
options: -l list containers
-p
Hi,
I have started using lxc to setup a pre-production system instead of KVM
at first glance clone seemd to me that it would copy everything to a new roots
but turns out that in case of LVM it will snapshot
AFAIK snapshots are meant more for backup or testing some changes and
discarding them later
i have a computer with 2 cores cpu. I want to create a container with 0.5
cpu. I found that cpuset.shares means how many time cpu time it get,
but i don't know whether cpuset.shares point to one cpu or all cpu?
if it points to one cpu, is the following configuratian right?
lxc.cgroup.cpuset.cpus =
hello Canhua,
I did apt-get bootstrap and installed it.
And now when i did ::
lxc-start -n vm0 [-f config file] -d
and after that i checked
lxc-info -n vm0
o/p was vm0 is stopped.
I did the same thing which is given in that site you mentioned.
Wrote all the things in config file which are given
Hi folks,
I've setup a full system container, without sys_admin capabilities.
Aside from any other side-effects this might have, I found that using
lxc-execute to run a single command inside the container no longer
works:
$ sudo lxc-execute -n template ls
lxc-init: failed to mount /proc :
You may have missed to lxc-create the container. You shoulld run:
lxc-create -n [container-name] -f [/path/to/config-file] -t [template-name]
for example lxc-create -n vm0 -f [lxc-veth.conf] -t debian
On Wed, Aug 24, 2011 at 10:17 PM, nishant mungse
wrote:
> hello Canhua,
> I did apt-get boots
according to my test cpu.shares just points to per cpu time, suppose you
have 3 container, A ,B, C :
A: lxc.cgroup.cpu.shares = 512
B: lxc.cgroup.cpu.shares = 512
C: lxc.cgroup.cpu.shares = 128
you run while(1) ++i; in A, B C. their cpu usage appears to be different
in machine having different cp
10 matches
Mail list logo