On Tue, Mar 17, 2015 at 01:50:37PM +0000, Peter Maydell wrote: > On 17 March 2015 at 10:02, fupan <fupan...@windriver.com> wrote: > > Did the qemu user mode support the systemd, cause I > > met the following error while start an arm lxc on x86-64: > > > > qemu: Unsupported syscall: 355 > > Failed to allocate manager object: Function not implemented > > 355 is signalfd4, which we don't currently implement. > A well designed userspace program will gracefully fall > back to some other implementation if it tries a newer > syscall but it doesn't exist.
systemd devs made an explicit decision to assume they have access to the level of functionality provided in Linux >= 3.7. So if we want QEMU user mode to support systemd, then at some point we'll need to implement signalfd4 support. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|