From: Keir Fraser <keir@xensource.com>
To: Chris <hap10@tycho.ncsc.mil>
Cc: xen-devel@lists.xensource.com, "George S. Coker,
II" <gscoker@alpha.ncsc.mil>
Subject: Re: [PATCH 0/8] Domain Groups: Introduction
Date: Wed, 21 Feb 2007 17:27:59 +0000 [thread overview]
Message-ID: <C202319F.9DE5%keir@xensource.com> (raw)
In-Reply-To: <45DC7E93.10107@tycho.ncsc.mil>
On 21/2/07 17:17, "Chris" <hap10@tycho.ncsc.mil> wrote:
> This is the part of the discussion I most wanted to have. Whatever
> mechanism you use to operate on a set of domains, life is better when
> the hypervisor is aware of the group abstraction. With a group-aware
> hypervisor there is a robustness gain because even if the entire control
> stack falls over, group data can be re-populated from the hypervisor.
There are other ways to store information in a way that persists across
daemon restarts. Like writing it to a file (perhaps via xenstored).
> Also, having group data managed in the hypervisor provides a level of
> separation between the group policy in the control stack and the
> management mechanism in the VMM.
A layered implementation, including separation of mechanism and policy, is
quite possible without putting the different layers at different privilege
levels.
> Although both Domain Groups and XSM can stand on their own merits
I'm not convinced! :-)
-- Keir
next prev parent reply other threads:[~2007-02-21 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 19:55 [PATCH 0/8] Domain Groups: Introduction Chris
2007-02-20 20:45 ` Daniel P. Berrange
2007-02-20 21:32 ` Chris
2007-02-20 22:56 ` Keir Fraser
2007-02-20 23:01 ` Ian Pratt
2007-02-20 23:23 ` Keir Fraser
2007-02-21 17:17 ` Chris
2007-02-21 17:27 ` Keir Fraser [this message]
2007-02-22 20:39 ` Chris
2007-02-22 21:01 ` Keir Fraser
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=C202319F.9DE5%keir@xensource.com \
--to=keir@xensource.com \
--cc=gscoker@alpha.ncsc.mil \
--cc=hap10@tycho.ncsc.mil \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.