[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] Chroot exec error inspite of qemu-static-arm being in

From: Urmish Ajit Thakker
Subject: Re: [Qemu-discuss] Chroot exec error inspite of qemu-static-arm being installed
Date: Thu, 23 Oct 2014 16:51:46 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0

Some more info -

I am running an Ubuntu 12.04 machine.

Disk Image is for armv8 architecture. (64 bit).

So my ls -l bin/ls gives me the following outout

bin/ls -> /bin/busybox.nosuid
And bin/busybox.nosuid exists in the mount directory.

I feel my qemu is old. But Ubuntu 12.04 does not have the latest package of qemu which can mount armv8. Does this make any sense?

On 10/23/14 13:07, Peter Maydell wrote:
On 23 October 2014 18:28, Urmish Ajit Thakker <address@hidden> wrote:
3) usr/bin/qemu-arm-static bin/ls
E - Error while loading bin/ls: No such file or directory

Note : bin/ls exists

4) sudo chroot . /usr/bin/qemu-arm-static /bin/ls
R - /bin/ls: Invalid ELF image for this architecture

5) sudo chroot . /bin/ls
R - chroot: failed to run command `/bin/ls': Exec format error

If I understand your instructions clearly, 3 & 4 should not happen. Am I
Correct, and this also shows that your problem is not related
to the binfmt-misc registration. It looks like your chroot does
not contain valid 32 bit ARM binaries. What does
  file /path/to/chroot/bin/ls
say? (if it says it's a symlink or something then find
a binary in the chroot that's a real target executable).

-- PMM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]