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

[Xen-API] vm.start() returns Fault 3 : invalid domain

To: xen-api@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-API] vm.start() returns Fault 3 : invalid domain
From: Saurabh Garg <saurabh.g.garg@xxxxxxxxxx>
Date: Mon, 28 Jan 2008 16:32:55 +0530
Delivery-date: Mon, 28 Jan 2008 03:04:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <173833770709120704k2fb5dd19x9e8608cec07da8e2@xxxxxxxxxxxxxx>
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: <173833770709120704k2fb5dd19x9e8608cec07da8e2@xxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.14 (Windows/20071210)
Hi,

I've used xen-api to create managed domain, and after creation the domain starts normally and comes up fine. However, when the domain is stopped (xm shutdown or using vm.cleanShutdown() from xen-api), it gets into a state "------", and the domain lists in the xm list.

VM is configured with the following actions:

on_crash preserve
on_poweroff restart
on_reboot restart

Showing up in the list seems to be fine as the domain is still registered with the xen management. But any subsequent attempts to start the domain using xen-spi calls (vm.spart()) result in an internal error stating "Fault 3 : '<DOM_ID>'". After this the xend service needs to be restarted to have the xen-api calls work correctly.

Such a virtual machine, however starts well using the "xm start" command, and the domid changes (usually to domid++).

Is this a known issue. To me it seems like the vm.cleanShutDown() (even tried hard shutdown) is not cleaning up the state of the vm correctly.

Any solutions or suggestions in this regard will be highly helpful.

Thanks in advance,
Saurabh.

Marinescu Dan wrote:
Hello,

I am trying to dynamically assign memory to a running Xen guest (Debian Etch from the template) using the Python bindings. The VM.set_memory_dynamic_max() doesn't seem to bring anything (i checked using free on the guest OS), while VM.set_memory_dynamic_max_live() throws the error XenAPI.Failure: VM_BAD_POWER_STATE. How can I do this?

Thanks,
Dan

------------------------------------------------------------------------

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


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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-API] vm.start() returns Fault 3 : invalid domain, Saurabh Garg <=