[Xen-API] Guest lifecycle via XenAPI

To:	xen-api@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-API] Guest lifecycle via XenAPI
From:	Matthias Blankenhaus <matthiasblankenhaus@xxxxxxxxx>
Date:	Tue, 19 Jul 2011 11:29:10 -0700 (PDT)
Delivery-date:	Tue, 19 Jul 2011 11:29:34 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1311100150; bh=SdkWL8n9sVRYs83ar+TQDAvVuwEeBMSr25wCRMyBjZo=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=VbucFQSN9coMKV6yJwYEZ5kS/I4HzLFrdcp0VI0OBlvpsSCXGEgLtkVKjJ+0xD/3YJjjFwLN+Lw6oWB9lugXtZMSflURBpEU2HR5px66yru4L0n+aq+bykssOKEWO4+fqP7EgDPtg7l0be3zTDwdNohkzrO0DMfP5RHpLsA416w=
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:MIME-Version:Content-Type; b=z3YnHh8PqE93lGH8DSXHOD6ii31dyzxX4Di4YmA9XguWJRz1Mmh3m5b534t25kAbRpuekR2Lg/bGJDx4ZZYXodcI7g/x5E05WG+6eixewxE5w3eByz0XGooWPQGYpGRBJVLV0JRxQZ82pUlj6vCkhKj9iG3/qRYqZCR4GmZcxuc=;
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-api-bounces@xxxxxxxxxxxxxxxxxxx

Howdy !

In order to use the Xen lifecycle for guests it appears that one has to use 'xm 
new <config>'  followed by 'xm start <config>'.  The XenAPI spec does not 
contain a VM method new.  How does one issue the equivalent of a 'xm new <cfg>' 
via XenAPI ?

Thanx,
Matthias

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api

WARNING - OLD ARCHIVES

xen-api

[Xen-API] Guest lifecycle via XenAPI