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/
Home Products Support Community News


Re: [Xen-API] New API Document and C Bindings

To: Stefan Berger <stefanb@xxxxxxxxxx>
Subject: Re: [Xen-API] New API Document and C Bindings
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Thu, 14 Sep 2006 06:23:25 +0100
Cc: Xen-API <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 13 Sep 2006 22:23:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <OFDEF196CA.CE66FA1B-ON852571E7.007F7B54-852571E7.007FDEBB@xxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <20060905124059.GE7810@xxxxxxxxxxxxxxxxxxxxxx> <OFDEF196CA.CE66FA1B-ON852571E7.007F7B54-852571E7.007FDEBB@xxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Sep 12, 2006 at 07:16:40PM -0400, Stefan Berger wrote:

> Also I have a question regarding domain-0. How will it be represented? Is
> it a VM - the fact that 'guest' is written in the description of the VM
> class makes me think that this might not be the case.

That's a very good question.  My instinct is to say that dom-0 shouldn't
be part of the list of domains, and that it should be considered part of
the infrastructure.  When we have driver domains, and HVM stub domains,
there will be many of these domains, representing different parts of the
infrastructure, and it seems to me that these are not the same as
"guests" or "VMs".  A VM can be rebooted, migrated (possibly), each time
keeping the same VM, but ending up with a different domain.  A VM is
ultimately the reason that users are running Xen, and the thing that
makes it useful.  For this reason, I don't think that domain 0 is a VM.

On the other hand, these things are still useful entities -- you might
want to monitor the CPU cost due to each of them, tweak their scheduling
parameters, and so on.  So perhaps they are close enough to being a VM
that we should put them in there, and cope with the slightly special
nature of them as best we can.

What do people think?


xen-api mailing list