I think I'm having a closely related problem: I can successfully log in, but if I then try to log in on another virtual terminal it hangs (sometimes running sudo commands will also hang). Running 'ps aux' with the working login reveals the following
root 617 2.2 0.1 4137736 5424 lxc/tty1 Ss+ 13:41 0:00 /usr/bin/qemu-arm-static /bin/login -- james so it's waiting in a system call. cat /proc/617/syscall then gives 44 0x4 0x7fb26bfcede8 0x61 0x4000 0x0 0x0 0x7fff4d2f6560 0x600f462d but I don't understand that output since Linux doesn't seem to have a system call numbered 44. I've tried this a few times and get the same result except that the 0x7f* parts are different, presumably the process memory layout is different. The 0x600f462d part stays fixed though. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1183429 Title: Hang on login after booting armhf container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1183429/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
