On 06/24/2010 09:43 PM, Papp Tamás wrote: > > Daniel Lezcano wrote, On 2010. 06. 24. 8:55: >> Console output is not defaulting to the current tty, so you have to >> specify >> >> lxc-start -n fsn -s lxc.console=$(tty) >> >> That will be fixed for 0.7.1, I will release probably tomorrow. > > I've just realized, what do you mean. > > My problem is not the lack of console messages, but the functionality. > It's just not working, for example I can't ping it. > > But right now this is the smaller problem. The bigger is that I cannot > stop or destroy it properly: > > $ lxc-start -l DEBUG -o $(tty) -n fsn -s lxc.console=$(tty) > lxc-start 1277408070.110 DEBUG lxc_conf - allocated pty > '/dev/pts/1' (4/5) > lxc-start 1277408070.110 DEBUG lxc_conf - allocated pty > '/dev/pts/2' (6/7) > lxc-start 1277408070.110 DEBUG lxc_conf - allocated pty > '/dev/pts/3' (8/9) > lxc-start 1277408070.110 DEBUG lxc_conf - allocated pty > '/dev/pts/4' (10/11) > lxc-start 1277408070.110 INFO lxc_conf - tty's configured > lxc-start 1277408070.111 DEBUG lxc_start - sigchild handler set > lxc-start 1277408070.111 INFO lxc_start - 'fsn' is initialized > lxc-start 1277408070.184 DEBUG lxc_cgroup - using cgroup > mounted at '/cgroup' > lxc-start 1277408070.184 ERROR lxc_cgroup - Device or resource > busy - failed to remove previous cgroup '/cgroup/fsn' > lxc-start: Device or resource busy - failed to remove previous cgroup > '/cgroup/fsn' > lxc-start 1277408070.184 ERROR lxc_start - failed to spawn 'fsn' > lxc-start: failed to spawn 'fsn' > lxc-start 1277408070.184 DEBUG lxc_cgroup - using cgroup > mounted at '/cgroup' > lxc-start 1277408070.184 ERROR lxc_cgroup - Device or resource > busy - failed to remove cgroup '/cgroup/fsn' > lxc-start: Device or resource busy - failed to remove cgroup > '/cgroup/fsn'
That's probably mean the container is already running. Did you checked with lxc-ps --name fsn ? > $ lxc-destroy -n fsn That will destroy the container, remove the container's configuration, rootfs, etc ... The cgroup is destroyed when the container exits not with lxc-destroy. At this point, you will have to create your container again. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
