can't login into armhf chroot

Bug #1188982 reported by Thomas Karl Pietrowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I created a armhf chroot and tried to login into it, but I get the message:

chroot: failed to run command 'bin/bash': No such file or directory

I followed these intructions:
https://wiki.ubuntu.com/ARM/RootfsFromScratch/QemuDebootstrap

Tried the same on Debian jessie using qemu 1.2.0 and it worked.

Are there now changes how to set up a armhf chroot?

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: qemu-user-static 1.4.0+dfsg-1expubuntu4
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
Uname: Linux 3.8.0-25-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sat Jun 8 18:38:42 2013
InstallationDate: Installed on 2013-02-10 (118 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MarkForUpload: True
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: qemu
UpgradeStatus: Upgraded to raring on 2013-02-10 (118 days ago)

Revision history for this message
Thomas Karl Pietrowski (thopiekar) wrote :
Revision history for this message
Thomas Karl Pietrowski (thopiekar) wrote :
Download full text (11.2 KiB)

Same when I use qemu-debootstrap:

thopiekar@thopiekar-hp:~/Arbeitsfläche$ sudo qemu-debootstrap raring --arch=armhf /chroots/armhf_qdebootstrap
I: Running command: debootstrap --arch armhf --foreign raring /chroots/armhf_qdebootstrap
I: Retrieving InRelease
I: Failed to retrieve InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 790BC7277767219C42C86F933B4FE6ACC0B21F32)
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on http://ports.ubuntu.com/ubuntu-ports...
I: Retrieving adduser
I: Validating adduser
I: Retrieving apt
I: Validating apt
I: Retrieving apt-utils
I: Validating apt-utils
I: Retrieving base-files
I: Validating base-files
I: Retrieving base-passwd
I: Validating base-passwd
I: Retrieving bash
I: Validating bash
I: Retrieving bsdutils
I: Validating bsdutils
I: Retrieving busybox-initramfs
I: Validating busybox-initramfs
I: Retrieving bzip2
I: Validating bzip2
I: Retrieving console-setup
I: Validating console-setup
I: Retrieving coreutils
I: Validating coreutils
I: Retrieving cpio
I: Validating cpio
I: Retrieving cron
I: Validating cron
I: Retrieving dash
I: Validating dash
I: Retrieving debconf
I: Validating debconf
I: Retrieving debconf-i18n
I: Validating debconf-i18n
I: Retrieving debianutils
I: Validating debianutils
I: Retrieving diffutils
I: Validating diffutils
I: Retrieving dmsetup
I: Validating dmsetup
I: Retrieving dpkg
I: Validating dpkg
I: Retrieving e2fslibs
I: Validating e2fslibs
I: Retrieving e2fsprogs
I: Validating e2fsprogs
I: Retrieving eject
I: Validating eject
I: Retrieving file
I: Validating file
I: Retrieving findutils
I: Validating findutils
I: Retrieving gcc-4.7-base
I: Validating gcc-4.7-base
I: Retrieving gnupg
I: Validating gnupg
I: Retrieving gpgv
I: Validating gpgv
I: Retrieving grep
I: Validating grep
I: Retrieving gzip
I: Validating gzip
I: Retrieving hostname
I: Validating hostname
I: Retrieving ifupdown
I: Validating ifupdown
I: Retrieving initramfs-tools
I: Validating initramfs-tools
I: Retrieving initramfs-tools-bin
I: Validating initramfs-tools-bin
I: Retrieving initscripts
I: Validating initscripts
I: Retrieving insserv
I: Validating insserv
I: Retrieving iproute
I: Validating iproute
I: Retrieving iputils-ping
I: Validating iputils-ping
I: Retrieving isc-dhcp-client
I: Validating isc-dhcp-client
I: Retrieving isc-dhcp-common
I: Validating isc-dhcp-common
I: Retrieving kbd
I: Validating kbd
I: Retrieving keyboard-configuration
I: Validating keyboard-configuration
I: Retrieving klibc-utils
I: Validating klibc-utils
I: Retrieving kmod
I: Validating kmod
I: Retrieving less
I: Validating less
I: Retrieving libacl1
I: Validating libacl1
I: Retrieving libapt-inst1.5
I: Validating libapt-inst1.5
I: Retrieving libapt-pkg4.12
I: Validating libapt-pkg4.12
I: Retrieving libattr1
I: Validating libattr1
I: Retrieving libaudit-common
I: Validating libaudit-common
I: Retrieving libaudit1
I: Validating libaudit1
I: Retrieving libblkid1
I: Validating libblkid1
I: Retrieving libbsd0
I: Validating libbsd0
I: Retrieving libbz2...

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

Thanks for reporting this bug.

Note that when I simply do

sudo lxc-create -t ubuntu -n a1 -- -a armhf

I can start and log into the armhf container with no problems. Reproducing with the RootfsFromScratch wiki page instructions.

Changed in qemu (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Thomas Karl Pietrowski (thopiekar) wrote :
Download full text (13.0 KiB)

seems that lxc-create executes the same command..

thopiekar@thopiekar-hp:~/armhf-test$ sudo lxc-create -t ubuntu -n a1 -- -a armhf

lxc-create: No config file specified, using the default config /etc/lxc/default.conf
Checking cache download in /var/cache/lxc/raring/rootfs-armhf ...
installing packages: vim,ssh,language-pack-de,language-pack-en
Downloading ubuntu raring minimal ...
I: Running command: debootstrap --arch armhf --foreign --verbose --components=main,universe --include=vim,ssh,language-pack-de,language-pack-en raring /var/cache/lxc/raring/partial-armhf
I: Retrieving InRelease
I: Failed to retrieve InRelease
I: Retrieving Release
I: Retrieving Release.gpg
I: Checking Release signature
I: Valid Release signature (key id 790BC7277767219C42C86F933B4FE6ACC0B21F32)
I: Retrieving Packages
I: Validating Packages
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found additional base dependencies: language-pack-de-base language-pack-en-base libedit2 libgpm2 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libkrb5-3 libkrb5support0 libpython2.7 libpython2.7-minimal libpython2.7-stdlib libwrap0 openssh-client openssh-server vim-runtime
I: Checking component main on http://ports.ubuntu.com/ubuntu-ports...
I: Retrieving adduser
I: Validating adduser
I: Retrieving apt
I: Validating apt
I: Retrieving apt-utils
I: Validating apt-utils
I: Retrieving base-files
I: Validating base-files
I: Retrieving base-passwd
I: Validating base-passwd
I: Retrieving bash
I: Validating bash
I: Retrieving bsdutils
I: Validating bsdutils
I: Retrieving busybox-initramfs
I: Validating busybox-initramfs
I: Retrieving bzip2
I: Validating bzip2
I: Retrieving console-setup
I: Validating console-setup
I: Retrieving coreutils
I: Validating coreutils
I: Retrieving cpio
I: Validating cpio
I: Retrieving cron
I: Validating cron
I: Retrieving dash
I: Validating dash
I: Retrieving debconf
I: Validating debconf
I: Retrieving debconf-i18n
I: Validating debconf-i18n
I: Retrieving debianutils
I: Validating debianutils
I: Retrieving diffutils
I: Validating diffutils
I: Retrieving dmsetup
I: Validating dmsetup
I: Retrieving dpkg
I: Validating dpkg
I: Retrieving e2fslibs
I: Validating e2fslibs
I: Retrieving e2fsprogs
I: Validating e2fsprogs
I: Retrieving eject
I: Validating eject
I: Retrieving file
I: Validating file
I: Retrieving findutils
I: Validating findutils
I: Retrieving gcc-4.7-base
I: Validating gcc-4.7-base
I: Retrieving gnupg
I: Validating gnupg
I: Retrieving gpgv
I: Validating gpgv
I: Retrieving grep
I: Validating grep
I: Retrieving gzip
I: Validating gzip
I: Retrieving hostname
I: Validating hostname
I: Retrieving ifupdown
I: Validating ifupdown
I: Retrieving initramfs-tools
I: Validating initramfs-tools
I: Retrieving initramfs-tools-bin
I: Validating initramfs-tools-bin
I: Retrieving initscripts
I: Validating initscripts
I: Retrieving insserv
I: Validating insserv
I: Retrieving iproute
I: Validating iproute
I: Retrieving iputils-ping
I: Validating iputils-ping
I: Retrieving isc-dhcp-client
I: Validating isc-dhcp-client
I: Retrieving isc-dhcp-common
I: Validating isc-dhcp-common
I: Re...

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

Likewise qemu-debootstrap works fine for me.

Could you show what 'dpkg -l | grep qemu' returns?

Changed in qemu (Ubuntu):
status: New → Incomplete
Revision history for this message
Thomas Karl Pietrowski (thopiekar) wrote :

thopiekar@thopiekar-hp:~$ dpkg -l | grep qemu
ii ipxe-qemu 1.0.0+git-4.d6b0b76-0ubuntu2 all Virtual package to support use of kvm-ipxe with qemu
ii qemu 1.4.0+dfsg-1expubuntu4 amd64 fast processor emulator
ii qemu-keymaps 1.4.0+dfsg-1expubuntu4 all QEMU keyboard maps
ii qemu-system 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries
ii qemu-system-arm 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries (arm)
ii qemu-system-common 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries (common files)
ii qemu-system-mips 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries (mips)
ii qemu-system-misc 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries (miscelaneous)
ii qemu-system-ppc 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries (ppc)
ii qemu-system-sparc 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries (sparc)
ii qemu-system-x86 1.4.0+dfsg-1expubuntu4 amd64 QEMU full system emulation binaries (x86)
ii qemu-user 1.4.0+dfsg-1expubuntu4 amd64 QEMU user mode emulation binaries
ii qemu-user-static 1.4.0+dfsg-1expubuntu4 amd64 QEMU user mode emulation binaries (static version)
ii qemu-utils 1.4.0+dfsg-1expubuntu4 amd64 QEMU utilities
ii scratchbox-devkit-qemu 0.13.90-0rabbit1 amd64 Qemu scratchbox devkit

Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 1188982] Re: can't login into armhf chroot

Thanks, this:

> ii scratchbox-devkit-qemu 0.13.90-0rabbit1 amd64 Qemu scratchbox devkit

appears to be the problem. When I install this, qemu-debootstrap
fails for me as well. When I remove it (and reboot, to make it
relinquish its binfmt bindings) it succeeds.

 status: invalid

Changed in qemu (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Thomas Karl Pietrowski (thopiekar) wrote :

well, removing only this package does not fix the problem, but purging the full scratchbox suite did the job.
Never thought that scratchbox might break qemu.

Thank you!

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.