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


[Xen-API] VM phase diagram

To: <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-API] VM phase diagram
From: "Uli Staerk" <Uli.Staerk@xxxxxxxxxxxxxx>
Date: Thu, 2 Aug 2007 20:18:20 +0200
Delivery-date: Thu, 02 Aug 2007 11:15:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfVMYFGIU7BYkgfQZumhTv8klWv6A==
Thread-topic: VM phase diagram

Hi, I have some questions on the different VM states.


1. I tried to redraw the state diagram and adding an additional state, representing a VM that has been killed by the console command vm destroy.


Is this correct? (hint: inline img following for all the text/plain readers ;-) )


2. What exactly is the Unknown state? Are there any state changes (and api calls) to recover an VM in the Unknown state – eg. into the halted state?


3. And what happens to a VM that gets hit by the VM.destroy? Is this VM completely deleted from the known space of the xend? So afterwards there is no way to re-create it without the config?


4. What commands does the console command vm destroy exactly do? Does he destroy the machine or just put it into the halted mode?



xen-api mailing list
<Prev in Thread] Current Thread [Next in Thread>