[Lxc-users] lxc-start on openvz tempate

[Papp Tamás]

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'


$ ls /cgroup/fsn
cgroup.procs          cpuset.mem_exclusive       
cpuset.sched_relax_domain_level  memory.limit_in_bytes            
memory.swappiness
cpuacct.stat          cpuset.mem_hardwall        
cpu.shares                       memory.max_usage_in_bytes        
memory.usage_in_bytes
cpuacct.usage         cpuset.memory_migrate      
devices.allow                    memory.memsw.failcnt             
memory.use_hierarchy
cpuacct.usage_percpu  cpuset.memory_pressure     
devices.deny                     memory.memsw.limit_in_bytes      
net_cls.classid
cpu.rt_period_us      cpuset.memory_spread_page  
devices.list                     memory.memsw.max_usage_in_bytes  
notify_on_release
cpu.rt_runtime_us     cpuset.memory_spread_slab  
freezer.state                    memory.memsw.usage_in_bytes      tasks
cpuset.cpu_exclusive  cpuset.mems                
memory.failcnt                   memory.soft_limit_in_bytes
cpuset.cpus           cpuset.sched_load_balance  
memory.force_empty               memory.stat

$ lxc-destroy -n fsn
$ ls /cgroup/fsn
cgroup.procs          cpuset.mem_exclusive       
cpuset.sched_relax_domain_level  memory.limit_in_bytes            
memory.swappiness
cpuacct.stat          cpuset.mem_hardwall        
cpu.shares                       memory.max_usage_in_bytes        
memory.usage_in_bytes
cpuacct.usage         cpuset.memory_migrate      
devices.allow                    memory.memsw.failcnt             
memory.use_hierarchy
cpuacct.usage_percpu  cpuset.memory_pressure     
devices.deny                     memory.memsw.limit_in_bytes      
net_cls.classid
cpu.rt_period_us      cpuset.memory_spread_page  
devices.list                     memory.memsw.max_usage_in_bytes  
notify_on_release
cpu.rt_runtime_us     cpuset.memory_spread_slab  
freezer.state                    memory.memsw.usage_in_bytes      tasks
cpuset.cpu_exclusive  cpuset.mems                
memory.failcnt                   memory.soft_limit_in_bytes
cpuset.cpus           cpuset.sched_load_balance  
memory.force_empty               memory.stat


I'm really confused:(

I user lxc on other Lucid servers with no problem.

tamas