WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 0/8] Domain Groups: Introduction

To: Chris <hap10@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/8] Domain Groups: Introduction
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Wed, 21 Feb 2007 17:27:59 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "George S. Coker, II" <gscoker@xxxxxxxxxxxxxx>
Delivery-date: Wed, 21 Feb 2007 09:27:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45DC7E93.10107@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdV3aGP4FyBmcHQEdu98AAX8io7RQ==
Thread-topic: [Xen-devel] [PATCH 0/8] Domain Groups: Introduction
User-agent: Microsoft-Entourage/11.2.5.060620
On 21/2/07 17:17, "Chris" <hap10@xxxxxxxxxxxxxx> 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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel