[Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?

[pgnet]

The statically linked qemu files in chroot are cp'd from the host env

        file $(which qemu-arm) $(which qemu-arm-binfmt)
                /usr/bin/qemu-arm:        ELF 64-bit LSB executable, x86-64, 
version 1 (GNU/Linux), statically linked, for GNU/Linux 3.0.0, 
BuildID[sha1]=a6c50ab9b8f1845daab2f41d85936712aabafd89, not stripped
                /usr/bin/qemu-arm-binfmt: ELF 64-bit LSB executable, x86-64, 
version 1 (GNU/Linux), statically linked, for GNU/Linux 3.0.0, 
BuildID[sha1]=ff78e29b45699433557fab5396b79f07211fd3d5, not stripped

where

        rpm -q --whatprovides $(which qemu-arm) $(which qemu-arm-binfmt)
                qemu-linux-user-2.10.1-412.1.x86_64
                qemu-linux-user-2.10.1-412.1.x86_64

pkg

        qemu-linux-user-2.10.1-412.1.x86_64

is sourced/installed from the openSUSE 'Virtualization' repo,

        https://build.opensuse.org/package/show/Virtualization/qemu-
linux-user

and,

        rpm -q --changelog qemu-linux-user-2.10.1-412.1.x86_64 | head -n 20
                * Thu Oct 19 2017 address@hidden
                - Patch queue updated from git://github.com/openSUSE/qemu.git 
opensuse-2.10
                  * Patches added:
                  0040-io-monitor-encoutput-buffer-size-fr.patch
                  0041-cirrus-fix-oob-access-in-mode4and5-.patch
                  0042-9pfs-use-g_malloc0-to-allocate-spac.patch

                * Tue Oct 03 2017 address@hidden
                - Update to v2.10.1 a stable, bug-fix-only release
                  * Patches dropped (upstream):
                  0034-slirp-fix-clearing-ifq_so-from-pend.patch
                  0035-s390-ccw-Fix-alignment-for-CCW1.patch
                  0038-s390x-ais-for-2.10-stable-disable-a.patch
                  0039-s390x-cpumodel-remove-ais-from-z14-.patch
                  * Patches renamed:
                  0036-target-i386-cpu-Add-new-EPYC-CPU-mo.patch
                  - > 0034-target-i386-cpu-Add-new-EPYC-CPU-mo.patch
                  0037-chardev-baum-fix-baum-that-releases.patch
                  - > 0035-chardev-baum-fix-baum-that-releases.patch
                  0040-io-fix-temp-directory-used-by-test-.patch

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1689367

Title:
  In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages.
  sys_getrandom ?

Status in QEMU:
  Incomplete

Bug description:
  On exec of an armv7 qemu chroot on my local x86_64 desktop, launched
  via

          /usr/sbin/qemu-binfmt-conf.sh

  from

          qemu-linux-user-2.9.0-374.1.x86_64

  on the host, inside the chroot any compile activity is laced with
  repetitions of

          qemu: Unsupported syscall: 384

  messages.

  This wasn't always the case -- but, TBH, it's been ~ 6 months since I
  used this env, and there have been scads of usual pkg updates in the
  interim.  These messages appear to be non-fatal, with no particular
  effect at all; at least not so far ...

  From a chat in #IRC,

        [10:05] davidgiluk clever/pgnd: I see it as getrandom
        [10:05] davidgiluk pgnd: 
https://fedora.juszkiewicz.com.pl/syscalls.html   sort it on the ARM table and 
you can easily see it
        [10:05] clever arch/arm/tools/syscall.tbl:384  common  getrandom        
       sys_getrandom
        [10:06] davidgiluk pgnd: my *guess* is that something is calling 
getrandom, getting told it's not implemented and then falling back to using 
/dev/urandom
        [10:10] pgnd davidgiluk: If that *is* the case, is it to be considered 
a problem, or just informational?
        [10:12] davidgiluk pgnd: As long as it's falling back probably 
informational; but someone should probably go and wire up sys_getrandom at some 
point

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1689367/+subscriptions