From: Thomas Huth <1884719@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1884719] Re: Function not implemented when using libaio
Date: Fri, 07 May 2021 02:52:48 -0000 [thread overview]
Message-ID: <162035596865.5967.18250361254218950575.malone@wampee.canonical.com> (raw)
In-Reply-To: 159289799812.6175.17000319886186623286.malonedeb@soybean.canonical.com
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting older bugs to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then please close this ticket as "Fix released".
If it is not fixed yet and you think that this bug report here is still
valid, then you have two options:
1) If you already have an account on gitlab.com, please open a new ticket
for this problem in our new tracker here:
https://gitlab.com/qemu-project/qemu/-/issues
and then close this ticket here on Launchpad (or let it expire auto-
matically after 60 days). Please mention the URL of this bug ticket on
Launchpad in the new ticket on GitLab.
2) If you don't have an account on gitlab.com and don't intend to get
one, but still would like to keep this ticket opened, then please switch
the state back to "New" within the next 60 days (otherwise it will get
closed as "Expired"). We will then eventually migrate the ticket auto-
matically to the new system (but you won't be the reporter of the bug
in the new system and thus won't get notified on changes anymore).
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1884719
Title:
Function not implemented when using libaio
Status in QEMU:
Incomplete
Bug description:
Hello
I experience "Function not implemented" errors when trying to use
Linux libaio library in foreign architecture, e.g. aarch64.
I've faced this problem while using https://github.com/multiarch/qemu-user-static, i.e. Docker+QEMU.
I understand that I do not use plain QEMU and you may count this report as a "distribution of QEMU"! Just let me know what are the steps to test it with plain QEMU and I will test and update this ticket!
Here are the steps to reproduce the issue:
1) On x86_64 machine register QEMU:
`docker run -it --rm --privileged multiarch/qemu-user-static
--reset --credential yes --persistent yes`
2) Start a Docker image with foreign CPU architecture, e.g. aarch64
`docker run -it arm64v8/centos:8 bash`
3) Inside the Docker container install GCC and libaio
`yum install gcc libaio libaio-devel`
4) Compile the following C program
```
#include <stdio.h>
#include <errno.h>
#include <libaio.h>
#include <stdlib.h>
struct io_control {
io_context_t ioContext;
};
int main() {
int queueSize = 10;
struct io_control * theControl = (struct io_control *) malloc(sizeof(struct io_control));
if (theControl == NULL) {
printf("theControl is NULL");
return 123;
}
int res = io_queue_init(queueSize, &theControl->ioContext);
io_queue_release(theControl->ioContext);
free(theControl);
printf("res is: %d", res);
}
```
```
cat > test.c
[PASTE THE CODE ABOVE HERE]
^D
```
`gcc test.c -o out -laio && ./out`
When executed directly on aarch64 machine (i.e. without emulation) or on x86_64 Docker image (e.g. centos:8) it prints `res is: 0`, i.e. it successfully initialized a LibAIO queue.
But when executed on Docker image with foreign/emulated CPU
architecture it prints `res is: -38` (ENOSYS). `man io_queue_init`
says that error ENOSYS is returned when "Not implemented."
Environment:
QEMU version: 5.0.0.2 (https://github.com/multiarch/qemu-user-static/blob/master/.travis.yml#L24-L28)
Container application: Docker
Output of `docker --version`:
```
Client:
Version: 19.03.8
API version: 1.40
Go version: go1.13.8
Git commit: afacb8b7f0
Built: Wed Mar 11 23:42:35 2020
OS/Arch: linux/amd64
Experimental: false
Server:
Engine:
Version: 19.03.8
API version: 1.40 (minimum version 1.12)
Go version: go1.13.8
Git commit: afacb8b7f0
Built: Wed Mar 11 22:48:33 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.3.3-0ubuntu2
GitCommit:
runc:
Version: spec: 1.0.1-dev
GitCommit:
docker-init:
Version: 0.18.0
GitCommit:
```
Same happens with Ubuntu (arm64v8/ubuntu:focal).
I've tried to `strace` it but :
```
/usr/bin/strace: ptrace(PTRACE_TRACEME, ...): Function not implemented
/usr/bin/strace: PTRACE_SETOPTIONS: Function not implemented
/usr/bin/strace: detach: waitpid(112): No child processes
/usr/bin/strace: Process 112 detached
```
Here are the steps to reproduce the problem with strace:
```
docker run --rm -it --security-opt seccomp:unconfined --security-opt apparmor:unconfined --privileged --cap-add ALL arm64v8/centos:8 bash
yum install -y strace`
strace echo Test
```
Note: I used --privileged, disabled seccomp and apparmor, and added
all capabilities
Disabling security solves the "Permission denied" problem but then
comes the "Not implemented" one.
Any idea what could be the problem and how to work it around ?
I've googled a lot but I wasn't able to find any problems related to libaio on QEMU.
Thank you!
Martin
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1884719/+subscriptions
next prev parent reply other threads:[~2021-05-07 3:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 7:39 [Bug 1884719] [NEW] Function not implemented when using libaio Martin Grigorov
2020-06-29 10:43 ` Stefan Hajnoczi
2020-06-29 10:43 ` Stefan Hajnoczi
2020-06-29 11:28 ` [Bug 1884719] " Laurent Vivier
2020-06-29 11:30 ` Laurent Vivier
2020-06-29 12:13 ` Martin Grigorov
2020-07-13 17:38 ` Martin Grigorov
2020-07-13 19:37 ` Laurent Vivier
2020-07-14 7:48 ` Martin Grigorov
2020-07-15 19:27 ` Laurent Vivier
2020-07-16 5:58 ` Martin Grigorov
2020-08-24 13:33 ` Martin Grigorov
2020-08-24 20:23 ` Laurent Vivier
2021-05-07 2:52 ` Thomas Huth [this message]
2021-05-07 6:35 ` Thomas Huth
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=162035596865.5967.18250361254218950575.malone@wampee.canonical.com \
--to=1884719@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).