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

[Xen-devel] How is xm list implemented?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Jiang Wang <jwangzju@xxxxxxxxx>
  • Date: Sun, 31 May 2009 15:54:25 -0400
  • Cc:
  • Delivery-date: Sun, 31 May 2009 12:54:52 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=xuCDLswQ7kK3CLrFqLp94X/qtTJfDRigjL5md5qHgxaKQOFEcQexDgy3RRf1Ch4LmD HcJpylXPHpWQmKrTClTjmjdWVFIFL0ISAVf2q44l1io8pdfPMTia5KxhFoEahB2LiIAN wKooYEXssJ7eub7NWVyG+nitjn2asaTukKilw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi:

I want to understand the implementation of xm list command, such as
which internal data structures are used. So far, I can only find out
that xm list is implemented by xend, and xend use Xen API,
VM.get_all(). But how is VM.get_all() implemented? Is it calling the
hypervisor? If so, which source file is for the implementation? Or it
is implemented in the xend itself? Any pointers? Thanks.

Regards,

Jiang

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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