Hello.
As far as I can tell, this is still an issue with the latest available
ubuntu, 18.04.2, which has: version 2.11.1(Debian 1:2.11+dfsg-
1ubuntu7.15)
Anyone know where I could get a newer version that would be compatible
with Ubuntu?
--
You received this bug notification because you are a m
Unfortunately I was only able to check in 3.1.
There is no problem with the call.
root@unit6:/mnt/build/chroot# dpkg -l | grep qemu-user-static
ii qemu-user-static
1:3.1+dfsg-5amd64QEMU user mode
emulation b
Thanks for that repro case with qemu-debootstrap and chroot. I can
confirm that I can repro this with QEMU version 2.11.1. However with
current head of git QEMU this is fixed -- the "unsupported syscall"
message is not printed. We added support for the renameat2 syscall in
commit 95d0307cc10ca3df87
Upgrading the kernel did not change the situation.
le9i0nx@unit6:~$ uname -a
Linux unit6 4.19.0-0.bpo.2-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.16-1~bpo9+1
(2019-02-07) x86_64 GNU/Linux
...
Updating certificates in /etc/ssl/certs...
qemu: Unsupported syscall: 382
0 added, 0 removed; done.
Running
Yes, you are right the application works correctly. At least the result
is expected.
Vesion kernel
le9i0nx@unit6:~$ uname -a
Linux unit6 4.9.0-8-rt-amd64 #1 SMP PREEMPT RT Debian 4.9.144-3.1 (2019-02-19)
x86_64 GNU/Linux
Host debian 9
quest debian 10
quest glib version
root@ddf2245902b3:/app# ap
...that said, we should implement renameat2 provided that the host
kernel does. What host kernel version are you using, and what host
kernel minimum requirement was the glibc for your guest compiled to
require? renameat2 was added in kernel 3.15, so if your host kernel is
older than this but your g
I don't suppose you have a testcase that doesn't require docker?
Syscall 382 is renameat2 for arm. Note that messages from QEMU about
unsupported syscalls are often harmless, because typically they only
appear for relatively new syscalls which QEMU hasn't implemented yet.
The guest code will have
