From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:54509)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1YXrxh-0001ra-7e
	for qemu-devel@nongnu.org; Tue, 17 Mar 2015 09:55:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1YXrxd-0002rw-Jh
	for qemu-devel@nongnu.org; Tue, 17 Mar 2015 09:55:13 -0400
Received: from mx1.redhat.com ([209.132.183.28]:42813)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <berrange@redhat.com>) id 1YXrxd-0002rW-DJ
	for qemu-devel@nongnu.org; Tue, 17 Mar 2015 09:55:09 -0400
Date: Tue, 17 Mar 2015 13:55:02 +0000
From: "Daniel P. Berrange" <berrange@redhat.com>
Message-ID: <20150317135502.GG6540@redhat.com>
References: <5507FBD1.4070603@windriver.com>
	<CAFEAcA8KfV7rAeG8k1U53XG5o67rXhyH6HaY4FSBH6T+1UEYqA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAFEAcA8KfV7rAeG8k1U53XG5o67rXhyH6HaY4FSBH6T+1UEYqA@mail.gmail.com>
Subject: Re: [Qemu-devel] did qemu-user mode support systemd
Reply-To: "Daniel P. Berrange" <berrange@redhat.com>
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: fupan <fupan.li@windriver.com>, QEMU Developers <qemu-devel@nongnu.org>

On Tue, Mar 17, 2015 at 01:50:37PM +0000, Peter Maydell wrote:
> On 17 March 2015 at 10:02, fupan <fupan.li@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 :|