From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51015) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bjpHW-0003uY-S3 for qemu-devel@nongnu.org; Tue, 13 Sep 2016 11:06:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bjpHR-0007PH-UT for qemu-devel@nongnu.org; Tue, 13 Sep 2016 11:05:53 -0400 Received: from indium.canonical.com ([91.189.90.7]:47343) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bjpHR-0007O0-Ou for qemu-devel@nongnu.org; Tue, 13 Sep 2016 11:05:49 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.76 #1 (Debian)) id 1bjpHQ-0003nX-8G for ; Tue, 13 Sep 2016 15:05:48 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id B70142E80CA for ; Tue, 13 Sep 2016 15:05:47 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Tue, 13 Sep 2016 14:56:50 -0000 From: Bilal Amarni <1623020@bugs.launchpad.net> Reply-To: Bug 1623020 <1623020@bugs.launchpad.net> Sender: bounces@canonical.com References: <20160913123400.2015.28467.malonedeb@wampee.canonical.com> Message-Id: <20160913145650.1703.82152.malone@wampee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1623020] Re: emulate amd64 binary on arm7 host List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org I see, I'll close the ticket then. Do you have any recommandation on how I could achieve this? It is actually a 64-bit CPU (armv8 from Raspberry Pi 3) but it's running on a 32-bit OS / kernel. ** Changed in: qemu Status: New =3D> Invalid -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1623020 Title: emulate amd64 binary on arm7 host Status in QEMU: Invalid Bug description: I'm trying to run a Go program compiled for amd64 on a Raspberry Pi. Here is an example : =3D=3D=3D // main.go package main func main() { println("hello world") } =3D=3D=3D Then here is the output I'm getting : =3D=3D=3D > GOARCH=3Damd64 go build main.go > ../qemu/build/x86_64-linux-user/qemu-x86_64 -strace ./main 29213 arch_prctl(4098,4823880,0,0,0,0) =3D 0 29213 write(2,0,4622922)fatal error: =3D 13 29213 write(2,0,4622132)bad timediv =3D 11 29213 write(2,0,4620094) =3D 1 29213 write(2,0,4635135)runtime: panic before malloc heap initialized =3D 46 29213 select(0,0,0,0,1082131776,0) =3D -1 errno=3D14 (Bad address) 29213 select(0,0,0,0,1082131776,0) =3D -1 errno=3D14 (Bad address) 29213 write(2,0,4623731) runtime stack: =3D 16 29213 write(2,0,4622922)fatal error: =3D 13 29213 write(2,0,4634607)gentraceback before goexitPC initialization =3D 43 29213 write(2,0,4620094) =3D 1 29213 write(2,0,4635135)runtime: panic before malloc heap initialized =3D 46 29213 write(2,0,4624923)panic during panic =3D 19 29213 write(2,0,4623731) runtime stack: =3D 16 29213 write(2,0,4622922)fatal error: =3D 13 29213 write(2,0,4634607)gentraceback before goexitPC initialization =3D 43 29213 write(2,0,4620094) =3D 1 29213 write(2,0,4635135)runtime: panic before malloc heap initialized =3D 46 29213 write(2,0,4627441)stack trace unavailable =3D 24 29213 exit_group(4) =3D=3D=3D I'm running the latest qemu (commit 7263da78045dc91cc207f350911efe4259e99b3c), which was compiled with "../configure --target-list=3Dx86_64-linux-user --static". The go version is 1.7.1, and the system "Linux raspberrypi 4.4.11-v7+ #888 SMP Mon May 23 20:10:33 BST 2016 armv7l GNU/Linux". To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1623020/+subscriptions