qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: qemu-devel@nongnu.org, Amarnath Valluri <amarnath.valluri@intel.com>
Subject: Re: [Qemu-devel] RFC: connecting chardev to a command forked by qemu
Date: Tue, 7 Nov 2017 09:23:22 +0000	[thread overview]
Message-ID: <20171107092322.GE14232@redhat.com> (raw)
In-Reply-To: <1510002125.22094.10.camel@intel.com>

On Mon, Nov 06, 2017 at 10:02:05PM +0100, Patrick Ohly wrote:
> On Mon, 2017-11-06 at 17:26 +0000, Daniel P. Berrange wrote:
> > I can see the argument about it making QEMU easier to use, and those
> > who care about security aren't forced to use this new feature. It
> > none the less has a cost on maintainers and existance of these
> > features does reflect on QEMU's security reputation even if many
> > don't use it.
> 
> With Yocto we really don't have much choice: we need a patch like this
> because the alternative (introducing support for spawning and stopping
> swtpm and then passing the right parameters to QEMU) is way more
> complex. So if this patch isn't acceptable to QEMU upstream, then I
> will keep it as simple as possible and propose it as a local patch in
> Yocto.

I don't really buy this argument. Any distro's core job is the ability
to start/stop/manage processes. Saying yocto is unable to manage
runing of swtpm is really dubious - it is simply a choice to declare
that it is QEMU's job. 

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-11-07  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 17:11 [Qemu-devel] RFC: connecting chardev to a command forked by qemu Patrick Ohly
2017-11-06 17:26 ` Daniel P. Berrange
2017-11-06 21:02   ` Patrick Ohly
2017-11-07  9:23     ` Daniel P. Berrange [this message]
2017-11-07  9:38       ` Patrick Ohly

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=20171107092322.GE14232@redhat.com \
    --to=berrange@redhat.com \
    --cc=amarnath.valluri@intel.com \
    --cc=patrick.ohly@intel.com \
    --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).