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][VTPM] Show vtpm with xm

To: aliguori@xxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH][VTPM] Show vtpm with xm
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Tue, 31 Jan 2006 14:37:00 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 31 Jan 2006 19:47:09 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43DED31B.2070206@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Anthony,

   the other format that is supported for printout in the sxp class is to print xml-style. Would that be better or is a format of

attribute = value

more friendly? The problem with attributes and values is that nesting - as it can obviously be done with S-_expression_ - is not so convenient to display.

Regards,
    Stefan

aliguori@xxxxxxxxxxxxxxxxxxxxxxx wrote on 01/30/2006 10:01:47 PM:

> I know all of the other devices spit out S-_expression_ outputs but
> perhaps we can spit something a little more friendly out.
>
> Regards,
>
> Anthony Liguori
>
> Stefan Berger wrote:
>
> >The attached patch adds 'xm vtpm-list <DomId>' functionality.
> >
> >Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxx>
> >
> >
> >  
> >
> >------------------------------------------------------------------------
> >
> >Index: root/xen-unstable.hg/tools/python/xen/xm/main.py
> >===================================================================
> >--- root.orig/xen-unstable.hg/tools/python/xen/xm/main.py
> >+++ root/xen-unstable.hg/tools/python/xen/xm/main.py
> >@@ -101,7 +101,7 @@ network_list_help = "network-list <DomId
> > vnet_list_help = "vnet-list [-l|--long]            list vnets"
> > vnet_create_help = "vnet-create <config>             create a vnet
> from a config file"
> > vnet_delete_help = "vnet-delete <vnetid>             delete a vnet"
> >-
> >+vtpm_list_help = "vtpm-list <DomId>                list virtual TPM devices"
> >
> > short_command_list = [
> >     "console",
> >@@ -165,6 +165,7 @@ device_commands = [
> >     "network-attach",
> >     "network-detach",
> >     "network-list",
> >+    "vtpm-list",
> >     ]
> >
> > vnet_commands = [
> >@@ -699,6 +700,14 @@ def xm_block_list(args):
> >         sxp.show(x)
> >         print
> >
> >+def xm_vtpm_list(args):
> >+    arg_check(args, "vtpm-list", 1)
> >+    dom = args[0]
> >+    from xen.xend.XendClient import server
> >+    for x in server.xend_domain_devices(dom, 'vtpm'):
> >+        sxp.show(x)
> >+        print
> >+
> > def xm_block_attach(args):
> >     arg_check(args, 'block-attach', 4, 5)
> >
> >@@ -834,6 +843,8 @@ commands = {
> >     "vnet-list": xm_vnet_list,
> >     "vnet-create": xm_vnet_create,
> >     "vnet-delete": xm_vnet_delete,
> >+    # vtpm
> >+    "vtpm-list": xm_vtpm_list,
> >     }
> >
> > ## The commands supported by a separate argument parser in xend.xm.
> >  
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >Xen-devel mailing list
> >Xen-devel@xxxxxxxxxxxxxxxxxxx
> >http://lists.xensource.com/xen-devel
> >  
> >
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>