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

[Xen-devel] Re: [PATCH] [XEND] alignment of vtpm support in xenapi, docu

To: Stefan Berger <stefanb@xxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] [XEND] alignment of vtpm support in xenapi, documentation and libxen
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 30 Jan 2007 15:32:40 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 30 Jan 2007 07:32:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <OF33D875DA.B6380259-ON85257273.00542821-85257273.0054847B@xxxxxxxxxx>
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>
References: <20070130151210.GC3261@xxxxxxxxxxxxxxxxxxxxxx> <OF33D875DA.B6380259-ON85257273.00542821-85257273.0054847B@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Jan 30, 2007 at 10:23:13AM -0500, Stefan Berger wrote:

> Ewan Mellor <ewan@xxxxxxxxxxxxx> wrote on 01/30/2007 10:12:10 AM:
> 
> > On Tue, Jan 30, 2007 at 09:29:47AM -0500, Stefan Berger wrote:
> >
> > > This patch aligns vTPM support in the Xen-API, documentation and
> lib-xen
> > > (after the recent changes).
> > >
> > > Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>
> >
> > What's the intention here?  You've removed the get_instance calls, but
> not the
> > instance field from the documentation.  Assuming that that's just a
> mistake,
> > and you meant to remove the instance field, we're left with a VTPM class
> that
> > has nothing other than a reference to a VM and a reference to a backend
> > domain.  What are the semantics of that object now?
> 
> The instance will remain to be assigned by the hotplug scripts. In the
> old-style of VM configuration file one could still pass it as parameter,
> but its ignored. I rather not have it passed in as a parameter by the
> Xen-API, either. From what I can see a getter for it is not useful,
> either, since I want the instance number to be hidden from management
> software.

What we're left with seems like a pretty expensive way of saying "VTPM_backend
= N".  Is there really nothing else that's configurable?  We could just put
this into VM.other_config if that's the only thing that you need, which would
make configuring a VTPM a lot easier.

Ewan.

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