[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsuppor
From: |
pgnet |
Subject: |
[Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ? |
Date: |
Fri, 03 Nov 2017 18:35:35 -0000 |
> Can you just run /usr/bin/qemu-arm-static --version in the chroot,
please ? (or whatever suse calls its statically linked binary).
Yep, as soon as I'm sitting back in front of the machine with the chroot
on it. Bit later ...
> The other interesting question is what version of the (host) kernel
headers the QEMU binary was built against -- if that's earlier than 3.17
then the headers won't define __NR_getrandom for the host system and we
won't implement the syscall.
The qemu build uses headers from a repo which tracks Kernel/Stable's
regular releases. It _currently_ holds kernel 4.13.10.
--
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
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?, Peter Maydell, 2017/11/03
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?, Peter Maydell, 2017/11/03
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?, pgnet, 2017/11/03
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?, Peter Maydell, 2017/11/03
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?, Peter Maydell, 2017/11/03
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?,
pgnet <=
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?, pgnet, 2017/11/03
- [Qemu-devel] [Bug 1689367] Re: In qemu chroot, repeating "qemu: Unsupported syscall: 384" messages. sys_getrandom ?, Peter Maydell, 2017/11/07