qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bilal Amarni <1623020@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1623020] Re: emulate amd64 binary on arm7 host
Date: Tue, 13 Sep 2016 14:56:50 -0000	[thread overview]
Message-ID: <20160913145650.1703.82152.malone@wampee.canonical.com> (raw)
In-Reply-To: 20160913123400.2015.28467.malonedeb@wampee.canonical.com

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 => 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 :

  ===
  // main.go
  package main

  func main() {
  	println("hello world")
  }
  ===

  Then here is the output I'm getting :

  ===
  > GOARCH=amd64 go build main.go
  > ../qemu/build/x86_64-linux-user/qemu-x86_64 -strace ./main
  29213 arch_prctl(4098,4823880,0,0,0,0) = 0
  29213 write(2,0,4622922)fatal error:  = 13
  29213 write(2,0,4622132)bad timediv = 11
  29213 write(2,0,4620094)
   = 1
  29213 write(2,0,4635135)runtime: panic before malloc heap initialized
   = 46
  29213 select(0,0,0,0,1082131776,0) = -1 errno=14 (Bad address)
  29213 select(0,0,0,0,1082131776,0) = -1 errno=14 (Bad address)
  29213 write(2,0,4623731)
  runtime stack:
   = 16
  29213 write(2,0,4622922)fatal error:  = 13
  29213 write(2,0,4634607)gentraceback before goexitPC initialization = 43
  29213 write(2,0,4620094)
   = 1
  29213 write(2,0,4635135)runtime: panic before malloc heap initialized
   = 46
  29213 write(2,0,4624923)panic during panic
   = 19
  29213 write(2,0,4623731)
  runtime stack:
   = 16
  29213 write(2,0,4622922)fatal error:  = 13
  29213 write(2,0,4634607)gentraceback before goexitPC initialization = 43
  29213 write(2,0,4620094)
   = 1
  29213 write(2,0,4635135)runtime: panic before malloc heap initialized
   = 46
  29213 write(2,0,4627441)stack trace unavailable
   = 24
  29213 exit_group(4)
  ===

  I'm running the latest qemu (commit
  7263da78045dc91cc207f350911efe4259e99b3c), which was compiled with
  "../configure --target-list=x86_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

  parent reply	other threads:[~2016-09-13 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 12:34 [Qemu-devel] [Bug 1623020] [NEW] emulate amd64 binary on arm7 host Bilal Amarni
2016-09-13 12:45 ` [Qemu-devel] [Bug 1623020] " Peter Maydell
2016-09-13 14:56 ` Bilal Amarni [this message]
2016-09-13 15:09   ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160913145650.1703.82152.malone@wampee.canonical.com \
    --to=1623020@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).