qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: fupan <fupan.li@windriver.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] did qemu-user mode support systemd
Date: Tue, 17 Mar 2015 13:55:02 +0000	[thread overview]
Message-ID: <20150317135502.GG6540@redhat.com> (raw)
In-Reply-To: <CAFEAcA8KfV7rAeG8k1U53XG5o67rXhyH6HaY4FSBH6T+1UEYqA@mail.gmail.com>

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 :|

  reply	other threads:[~2015-03-17 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 10:02 [Qemu-devel] did qemu-user mode support systemd fupan
2015-03-17 13:50 ` Peter Maydell
2015-03-17 13:55   ` Daniel P. Berrange [this message]
2015-03-17 13:58     ` Peter Maydell

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=20150317135502.GG6540@redhat.com \
    --to=berrange@redhat.com \
    --cc=fupan.li@windriver.com \
    --cc=peter.maydell@linaro.org \
    --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).