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] VM phase diagram

To: Uli Staerk <Uli.Staerk@xxxxxxxxxxxxxx>
Subject: Re: [Xen-API] VM phase diagram
From: Jim Fehlig <jfehlig@xxxxxxxxxx>
Date: Fri, 03 Aug 2007 15:39:49 -0600
Cc: xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 03 Aug 2007 14:37:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <F91A18B8B41BEA4496988E928B3AAE6D54E4DF@xxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <F91A18B8B41BEA4496988E928B3AAE6D54E4DF@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (X11/20060911)
Uli Staerk wrote:
> 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 ;-) )

I don't think you need such a state.  'xm destroy' is just a
hard-shutdown of the vm, analogous to pulling the power cord on a
physical system.  Notice you can go from running to halted state using
hardShutdown (xm destroy) transition.

> 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?

I haven't actually seen a vm in this state so don't know.  My guess is
you could still move the vm to other states.  At minimum it could be
deleted and created (or new'ed) again.

>  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?

The vm transitions to powered off state.  It can be started again with
'xm start domname'.  It is still under control of xend.

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

Pulls the plug on the vm, causing it to transition to powered down state.


xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>