[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1777226] Re: qemu-user warnings confuse userland appli
From: |
Peter Maydell |
Subject: |
[Qemu-devel] [Bug 1777226] Re: qemu-user warnings confuse userland applications |
Date: |
Fri, 06 Jul 2018 12:40:49 -0000 |
Yes, we should probably move these "unimplemented syscall" warnings to
the LOG_UNIMP logging level (which you can then turn on if you want
them).
** Tags added: linux-user
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1777226
Title:
qemu-user warnings confuse userland applications
Status in QEMU:
Confirmed
Bug description:
I recently observed that warning messages emitted by qemu-user can
confuse applications when reading from stdout/stderr. This was
observed with the configure script of OpenJDK-11 on qemu-sh4:
configure: Found potential Boot JDK using configure arguments
configure: Potential Boot JDK found at /usr/lib/jvm/java-10-openjdk-sh4 is
incorrect JDK version (qemu: Unsupported syscall: 318); ignoring
configure: (Your Boot JDK version must be one of: 10 11)
configure: error: The path given by --with-boot-jdk does not contain a valid
Boot JDK
configure exiting with result code 1
See:
https://buildd.debian.org/status/fetch.php?pkg=openjdk-11&arch=sh4&ver=11%7E18-1&stamp=1529119043&raw=0
Commenting out the line of code which emits the warning fixes the
problem for me and the configure script finishes without problems.
Thus, qemu should be modified to avoid cluttering stdout or stderr
with its own messages and rather send those warnings to a log file or
similar.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1777226/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [Bug 1777226] Re: qemu-user warnings confuse userland applications,
Peter Maydell <=