Hang on login after booting armhf container

Bug #1183429 reported by Rune K. Svendsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Expired
High
Unassigned

Bug Description

I create an armhf container using the following command:

    sudo lxc-create -n armhf01 -t ubuntu — -a armhf -r precise

I then start it like so:

    sudo lxc-start -n armhf01

It boots up, shows a lot of

    <process name> main process terminated with status <num>

messages on the console (which I've read are fine)

and I arrive at the login prompt, where I try to log in with the default ubuntu/ubuntu login. After entering this information, the following information is output to the terminal:

    Last login: Thu May 23 15:24:20 UTC 2013 on lxc/console
    Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 2.6.32 armv7l)

     * Documentation: https://help.ubuntu.com/

and it just sits there, with a blinking cursor.

The machine is running, I can see with lxc-ls:

    NAME STATE IPV4 IPV6 AUTOSTART
    ---------------------------------------------
    armhf01 RUNNING 10.0.3.211 - NO

although it doesn't seem to have gotten a LAN IP.

If I try to login via ssh, it also hangs, but this is aborted after a while with a "broken pipe" message:

    The authenticity of host '10.0.3.211 (10.0.3.211)' can't be established.
    ECDSA key fingerprint is 36:bd:9d:98:a3:d6:2a:fc:9f:f2:33:a8:00:46:17:9e.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added '10.0.3.211' (ECDSA) to the list of known hosts.
    ubuntu@10.0.3.211's password:
    Write failed: Broken pipe

I'm attaching the debug output file created by starting the container like so:

    sudo lxc-start -n armhf01 -l debug -o output

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: lxc 0.9.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
Uname: Linux 3.8.0-21-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Thu May 23 17:52:38 2013
InstallationDate: Installed on 2012-06-09 (347 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
SourcePackage: lxc
UpgradeStatus: Upgraded to raring on 2013-05-03 (19 days ago)

Revision history for this message
Rune K. Svendsen (runeks) wrote :
Revision history for this message
Rune K. Svendsen (runeks) wrote :
Revision history for this message
Stéphane Graber (stgraber) wrote :

Moving to qemu as LXC isn't doing anything special here so chances are that it's the qemu-arm-static hanging for some reason.

affects: lxc (Ubuntu) → qemu (Ubuntu)
Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

arm1 root 21838 21593 0 09:43 ? 00:00:00 /usr/bin/qemu-arm-static /bin/sh /etc/network/if-up.d/ntpdate
arm1 root 21843 21838 0 09:43 ? 00:00:00 /usr/bin/qemu-arm-static /usr/bin/lockfile-touch /var/lock/ntpdate-ifup
arm1 root 21845 21838 0 09:43 ? 00:00:00 /usr/bin/qemu-arm-static /usr/sbin/ntpdate -s ntp.ubuntu.com
arm1 root 21850 21593 0 09:43 ? 00:00:00 /usr/bin/qemu-arm-static /usr/sbin/sshd -D
arm1 root 21876 21593 0 09:43 pts/11 00:00:00 /usr/bin/qemu-arm-static /sbin/getty -8 38400 tty4
arm1 root 21878 21593 0 09:43 pts/8 00:00:00 /usr/bin/qemu-arm-static /sbin/getty -8 38400 tty2
arm1 root 21879 21593 0 09:43 pts/9 00:00:00 /usr/bin/qemu-arm-static /sbin/getty -8 38400 tty3
arm1 root 21881 21593 0 09:43 ? 00:00:00 /usr/bin/qemu-arm-static /usr/sbin/cron
arm1 root 21910 21593 0 09:43 pts/12 00:00:00 /usr/bin/qemu-arm-static /bin/login -- ubunu
arm1 root 21912 21593 0 09:43 pts/6 00:00:00 /usr/bin/qemu-arm-static /bin/login -- ubuntu
arm1 root 21593 21587 0 09:42 ? 00:00:00 /sbin/init
arm1 root 21693 21593 0 09:42 ? 00:00:00 upstart-socket-bridge --daemon
arm1 root 21738 21593 0 09:42 ? 00:00:00 upstart-udev-bridge --daemon
arm1 root 21785 21593 0 09:42 ? 00:00:00 /usr/bin/qemu-arm-static /usr/sbin/rsyslogd -c5
arm1 root 21828 21593 0 09:43 ? 00:00:00 dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -1 eth0

The above is with an attempt to login on /dev/console and another on tty1. Both are hanging at login.

Changed in qemu (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
JamesL (jamesly0n) wrote :

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.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Can you still reproduce this in 14.04 or 15.10?

Changed in qemu (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]

Changed in qemu (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.