qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: berrange@redhat.com, mprivozn@redhat.com
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	bryntcor@us.ibm.com, libvir-list@redhat.com,
	Marcelo Cerri <mhcerri@linux.vnet.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	gcwilson@us.ibm.com, eblake@redhat.com
Subject: Re: [Qemu-devel] [libvirt] [PATCH v4 0/5] Per-guest configurable user/group for QEMU processes
Date: Tue, 11 Sep 2012 14:13:38 -0400	[thread overview]
Message-ID: <504F7F52.2010809@linux.vnet.ibm.com> (raw)
In-Reply-To: <1345068639-19528-1-git-send-email-mhcerri@linux.vnet.ibm.com>

Are there any other requirements that need to be taken care of to enable 
execution of QEMU guests under separate unprivileged user IDs (ie. DAC 
isolation)?

At this point, this patch series (Per-guest configurable user/group for 
QEMU processes) is upstream, allowing libvirt to execute guests under 
separate unprivileged user IDs.  Additionally, the QEMU bridge helper 
series is upstream, allowing QEMU to allocate a tap device and attach it 
to a bridge when run under an unprivileged user ID 
(http://www.redhat.com/archives/libvir-list/2012-August/msg00277.html).

Is there any other feature in QEMU that requires QEMU to be run as root?

-- 
Regards,
Corey

On 08/15/2012 06:10 PM, Marcelo Cerri wrote:
> This is a v4 patch series that updates the libvirt's security driver mechanism to support per-guest configurable user and group for QEMU processes running together with other security drivers, such as SELinux and AppArmor.
>
> Marcelo Cerri (5):
>    Internal refactory of data structures
>    Multiple security drivers in XML data
>    Update security layer to handle many security labels
>    Support for multiple default security drivers in QEMU config
>    Update the remote API
>
>   daemon/remote.c                                    |   63 ++++
>   docs/formatdomain.html.in                          |   11 +-
>   docs/schemas/capability.rng                        |   18 +-
>   docs/schemas/domaincommon.rng                      |   30 ++-
>   include/libvirt/libvirt.h.in                       |    2 +
>   python/generator.py                                |    1 +
>   src/conf/capabilities.c                            |   17 +-
>   src/conf/capabilities.h                            |    6 +-
>   src/conf/domain_audit.c                            |   14 +-
>   src/conf/domain_conf.c                             |  343 +++++++++++++++-----
>   src/conf/domain_conf.h                             |   20 +-
>   src/driver.h                                       |    4 +
>   src/libvirt.c                                      |   47 +++
>   src/libvirt_private.syms                           |    5 +
>   src/libvirt_public.syms                            |    1 +
>   src/lxc/lxc_conf.c                                 |    8 +-
>   src/lxc/lxc_controller.c                           |    8 +-
>   src/lxc/lxc_driver.c                               |   11 +-
>   src/lxc/lxc_process.c                              |   23 +-
>   src/qemu/qemu.conf                                 |    6 +-
>   src/qemu/qemu_conf.c                               |   38 ++-
>   src/qemu/qemu_conf.h                               |    2 +-
>   src/qemu/qemu_driver.c                             |  218 +++++++++++---
>   src/qemu/qemu_process.c                            |   50 ++-
>   src/remote/remote_driver.c                         |   46 +++
>   src/remote/remote_protocol.x                       |   17 +-
>   src/remote_protocol-structs                        |   11 +
>   src/security/security_apparmor.c                   |  118 +++++--
>   src/security/security_dac.c                        |  324 +++++++++++++++++--
>   src/security/security_manager.c                    |  101 +++++--
>   src/security/security_manager.h                    |    8 +-
>   src/security/security_selinux.c                    |  263 +++++++++++-----
>   src/security/security_stack.c                      |  237 +++++++++-----
>   src/security/security_stack.h                      |   13 +
>   src/test/test_driver.c                             |   11 +-
>   .../qemuxml2argv-seclabel-dynamic-override.xml     |    4 +-
>   .../qemuxml2argv-seclabel-dynamic.xml              |    2 +-
>   37 files changed, 1653 insertions(+), 448 deletions(-)
>
> --
> libvir-list mailing list
> libvir-list@redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list
>

       reply	other threads:[~2012-09-11 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1345068639-19528-1-git-send-email-mhcerri@linux.vnet.ibm.com>
2012-09-11 18:13 ` Corey Bryant [this message]
2012-09-13 20:36   ` [Qemu-devel] [libvirt] [PATCH v4 0/5] Per-guest configurable user/group for QEMU processes Marcelo Cerri
2012-09-14  8:40   ` Daniel P. Berrange
2012-09-14 13:31     ` Corey Bryant
2012-09-14 13:51       ` Daniel P. Berrange
2012-09-14 14:44         ` Corey Bryant

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=504F7F52.2010809@linux.vnet.ibm.com \
    --to=coreyb@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=berrange@redhat.com \
    --cc=bryntcor@us.ibm.com \
    --cc=eblake@redhat.com \
    --cc=gcwilson@us.ibm.com \
    --cc=libvir-list@redhat.com \
    --cc=mhcerri@linux.vnet.ibm.com \
    --cc=mprivozn@redhat.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).