As a quick follow-up, when I built and installed the latest git master, this issue no longer occurs. 

Some other things I noticed: 
- if I lxc-start without daemonize, as mentioned it hangs without showing the console login prompt.  But if I interrupt it with Ctrl+C, the host reboots. 
- in the same scenario if I 'kill -9' lxc-start, no host reboot occurs.
- lxc-stop also causes a host reboot, but lxc-destroy -f of the running instance does not.  
- in the working build off of master, the "permission denied" output  I reported in the original message does not occur. 
 
Please let me know if there's anything else I can do/provide  to help hunt this down. 
 


On Sat, Oct 26, 2013 at 4:06 PM, Marc Paradise <m...@opscode.com> wrote:


On Fri, Oct 25, 2013 at 10:30 AM, Serge Hallyn <serge.hal...@ubuntu.com> wrote:

Can you please do an lxc-start with '-l info -o outfile' options and
attach the outfile?  Also show the /proc/self/mounts and
/proc/self/mountinfo contents from both the host and the container.

I've attached mountinfo and mounts from the host, but I can't reach the guest via console or ssh to grab the same there.  Log is also attached. 


Thanks for taking a look. 




--
Marc Paradise 
Software Engineer
Opscode

Twitter: @MarcParadise
irc: mparadise
Skype: marc.paradise


------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Lxc-users mailing list
Lxc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxc-users

Reply via email to