From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Ian.Jackson@eu.citrix.com,
Dario Faggioli <dario.faggioli@citrix.com>,
xen-devel@lists.xensource.com, wei.liu2@citrix.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v6] run QEMU as non-root
Date: Thu, 09 Jul 2015 17:14:40 -0600 [thread overview]
Message-ID: <559F0060.5020201@suse.com> (raw)
In-Reply-To: <1436438045.23508.101.camel@citrix.com>
On 07/09/2015 04:34 AM, Ian Campbell wrote:
> On Wed, 2015-07-01 at 15:03 -0600, Jim Fehlig wrote:
>> Perhaps. But thanks for providing a way (b_info->device_model_user) for apps to
>> override the libxl policy.
> You mentioned in v5 that libvirt supports setting both the user and the
> group and that the qemu driver supports that. How does that work?
>
> AFAICT qemu's -runas option only takes a user and it takes that user's
> primary group and uses that with no configurability. I think that's a
> fine way to do things, but you implied greater configurability in
> libvirt and I'm now curious...
The libvirt qemu driver doesn't use qemu's -runas option. It calls
setregid()/setreuid() in the child after fork()'ing, but before exec()'ing, qemu.
Regards,
Jim
next prev parent reply other threads:[~2015-07-09 23:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 12:50 [PATCH v6] run QEMU as non-root Stefano Stabellini
2015-07-01 15:29 ` Dario Faggioli
2015-07-01 15:34 ` Stefano Stabellini
2015-07-01 21:03 ` Jim Fehlig
2015-07-09 10:34 ` Ian Campbell
2015-07-09 23:14 ` Jim Fehlig [this message]
2015-07-10 8:40 ` Ian Campbell
2015-07-09 10:31 ` Ian Campbell
2015-07-23 17:04 ` Stefano Stabellini
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=559F0060.5020201@suse.com \
--to=jfehlig@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).