[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-API] domains created through API do not show dom id

  • To: xen-users@xxxxxxxxxxxxxxxxxxx, xen-api@xxxxxxxxxxxxxxxxxxx
  • From: "suyash jape" <suyashjape@xxxxxxxxx>
  • Date: Sat, 6 Oct 2007 20:19:17 +0530
  • Delivery-date: Sat, 06 Oct 2007 07:49:45 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=L7xHmx6ooloFC0A4C/t72iIwE6QA4Js18WRLEQ2tkJJKFEeK/xzOajkI/l9+mTFORu+F34afk+eICN3O6RKpSSTUX2qwd82uDZhRnCkId8XEwgAku3HRUDN9/MZ60c+vTnl/0sUszpuOiWcqluWEQMAjSxpvMMSM1WAi9mXJivI=
  • List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>

Hi all
  I am using XenAPI (port 9363) to create new domains through ruby scripting...Xen is a registered package(gem) in ruby which provides an interface to the XenAPI.Its quite basic as compared to the python bindings.

Domains created in this way do not show any domain  Id ....after inspecting the XML RPC messages , i found that these doamins have dom id = -1 ..i.e  idle domains to my understanding.

I am not able to xm destroy/shutdown/restart or control these domains in any way.These domains remain in xm list even after i reboot the machine.

1) Any suggestions regarding this ..or What to do with idle domains
   Heres wht i found about idle domains :
"Dom idle
denote a special idle domain that "executes" on the
CPU when there are no other runnable domains (i.e. there is
no virtual machine that is not-blocked and not-idle). Dom
is the analog to the "idle-loop" executed by an OS when there
are no other runnable processes."

2) Are domains created through API different from those created from config file?
How do they differ ...is this what is managed and unmanaged domains ?

xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.