Re: [Lxc-users] natty without network isolation
Quoting webcubator webcubator (webcuba...@mail.ru): Hello! Shortly... I want to install natty as guest without network isolation The problem is lxc-start hangs in this case If I add network all works fine With this network settings all works fine -- cut -- lxc.network.type=veth -- ent cut -- But network is isolated and I doesn't want to isolate network Bellow details, what I do exactly: # dpkg -l | grep lxc ii lxc 0.7.4-0ubuntu7.1 Linux containers userspace tools # uname -a Linux XXX 2.6.38-8-virtual #42-Ubuntu SMP Mon Apr 11 07:04:38 UTC 2011 i686 i686 i386 GNU/Linux # lxc-create -t natty -n natty01 Don't do it with no lxc.conf (-f), rather use something like /usr/share/doc/lxc/examples/lxc-empty-netns.conf: # Container with new network withtout network devices lxc.utsname = omega lxc.network.type = empty lxc.network.flags = up -serge -- Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
[Lxc-users] natty without network isolation
Hello! Shortly... I want to install natty as guest without network isolation The problem is lxc-start hangs in this case If I add network all works fine With this network settings all works fine -- cut -- lxc.network.type=veth -- ent cut -- But network is isolated and I doesn't want to isolate network Bellow details, what I do exactly: # dpkg -l | grep lxc ii lxc 0.7.4-0ubuntu7.1 Linux containers userspace tools # uname -a Linux XXX 2.6.38-8-virtual #42-Ubuntu SMP Mon Apr 11 07:04:38 UTC 2011 i686 i686 i386 GNU/Linux # lxc-create -t natty -n natty01 Warning: --- Usually the template option is called with a configuration file option too, mostly to configure the network. eg. lxc-create -n foo -f lxc.conf -t debian The configuration file is often: lxc.network.type=macvlan lxc.network.link=eth0 lxc.network.flags=up or alternatively: lxc.network.type=veth lxc.network.link=br0 lxc.network.flags=up For more information look at lxc.conf (5) At this point, I assume you know what you do. Press enter to continue ... ... press enter here ... debootstrap is /usr/sbin/debootstrap Checking cache download in /var/cache/lxc/natty/rootfs-i386 ... ... skipped ... 'natty01' created # lxc-start -n natty01 -o log -l debug -- /sbin/init --verbose init: Handling startup event init: mountall goal changed from stop to start init: mountall state changed from waiting to starting init: hostname goal changed from stop to start init: hostname state changed from waiting to starting init: Handling starting event init: plymouth goal changed from stop to start init: plymouth state changed from waiting to starting init: hwclock goal changed from stop to start init: hwclock state changed from waiting to starting init: lxcmount goal changed from stop to start init: lxcmount state changed from waiting to starting init: Handling starting event init: hostname state changed from starting to pre-start init: hostname state changed from pre-start to spawned init: hostname main process (2) init: hostname state changed from spawned to post-start init: hostname state changed from post-start to running init: Handling starting event init: plymouth state changed from starting to pre-start init: plymouth state changed from pre-start to spawned init: plymouth main process (3) init: Handling starting event init: hwclock state changed from starting to pre-start init: hwclock state changed from pre-start to spawned init: hwclock main process (4) init: hwclock state changed from spawned to post-start init: hwclock state changed from post-start to running init: Handling starting event init: lxcmount state changed from starting to pre-start init: lxcmount pre-start process (5) init: Handling started event init: Handling started event init: hostname main process (2) exited normally init: hostname goal changed from start to stop init: hostname state changed from running to stopping init: lxcmount pre-start process (5) exited normally init: lxcmount state changed from pre-start to spawned init: lxcmount main process (6) init: lxcmount state changed from spawned to post-start init: lxcmount state changed from post-start to running init: hwclock main process (4) exited normally init: hwclock goal changed from start to stop init: hwclock state changed from running to stopping init: Handling stopping event init: hostname state changed from stopping to killed init: hostname state changed from killed to post-stop init: hostname state changed from post-stop to waiting init: Handling started event init: Handling stopping event init: hwclock state changed from stopping to killed init: hwclock state changed from killed to post-stop init: hwclock state changed from post-stop to waiting init: Handling stopped event init: Handling stopped event init: plymouth main process (3) executable changed init: lxcmount main process (6) exited normally init: lxcmount goal changed from start to stop init: lxcmount state changed from running to stopping init: plymouth main process (3) became new process (7) init: plymouth state changed from spawned to post-start init: plymouth post-start process (8) init: Handling stopping event init: lxcmount state changed from stopping to killed init: lxcmount state changed from killed to post-stop init: lxcmount state changed from post-stop to waiting init: Handling stopped event init: plymouth post-start process (8) exited normally init: plymouth state changed from post-start to running init: mountall state changed from starting to pre-start init: mountall state changed from pre-start to spawned init: mountall main process (9) init: Handling started event init: mountall main process (9) executable changed init: mountall main process (9) became new process (10) init: mountall main process (10) became new process (11) init: mountall state changed from spawned to post-start init: mountall state changed from post-start to running init:
