Fix has been committed upstream.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1470170
Title:
Unsupported syscalls 370 and 355
Status in QEM
Laurent,
I just encountered the same missing syscall on qemu-m68k:
Unpacking udev (228-2) over (227-2) ...
Preparing to unpack .../libsystemd0_228-2_m68k.deb ...
Unpacking libsystemd0:m68k (228-2) over (227-2) ...
Processing triggers for man-db (2.7.5-1) ...
Not building database; man-db/auto-upd
Le 30/06/2015 19:49, Peter Maydell a écrit :
> Syscall 370 is name_to_handle_at, and 355 is signalfd4. (Likely if
> name_to_handle_at succeeds then it'll want open_by_handle_at too.)
>
> This patch implements the signalfd syscalls, though we haven't got to
> reviewing it yet.
> http://patchwork
Syscall 370 is name_to_handle_at, and 355 is signalfd4. (Likely if
name_to_handle_at succeeds then it'll want open_by_handle_at too.)
This patch implements the signalfd syscalls, though we haven't got to reviewing
it yet.
http://patchwork.ozlabs.org/patch/478072/
It looks like systemd is coping
