Many thanks!

I've just compiled master, and docker/aarch64/openjdk image now works as
expected on my x86 machine.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  qemu-aarch64-static docker arm64v8/openjdk coredump

Status in QEMU:
  Fix Committed

Bug description:
  I am using qemu-aarch64-static to run the arm64v8/openjdk official
  image on my x86 machine. Using QEMU master, I immediately hit a bug
  which hangs the container. With Ubuntu default version qemu-aarch64
  version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.24) and qemu-aarch64
  version 2.11.1 (v2.11.1-dirty) the hang does not take place.

  To reproduce (and get to the core dump):

  $ /tmp/tmptgyg3nvh/qemu-aarch64-static/qemu-aarch64-static -version
  qemu-aarch64 version 2.11.91 (v2.12.0-rc1-5-g47d3b60-dirty)
  Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

  $ docker run -it -v 
arm64v8/openjdk /bin/bash
  root@bf75cf45d311:/# javac
  Usage: javac <options> <source files>
  where possible options include:
    -g                         Generate all debugging info
    @<filename>                Read options and filenames from file

  qemu: uncaught target signal 11 (Segmentation fault) - core dumped

  To get the core dump, In a separate terminal:

  # snapshot the file system of the hung image
  $ docker commit $(docker ps -aqf "name=latest_qemu") qemu_coredump

  # connect with known working qemu
  $ docker run -t -v /usr/bin/qemu-aarch64-static:/usr/bin/qemu-aarch64-static  
-i qemu_coredump /bin/bash

  $$ ls -lat
  total 10608
  -rw-r--r--   1 root root 10792960 Mar 29 18:02 
  drwxrwxrwt   5 root root     4096 Mar 29 18:02 tmp

To manage notifications about this bug go to:

Reply via email to