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

[Xen-users] virsh vs. xm, and questions about different distributions of Xen

  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "David Stone" <unclestoner@xxxxxxxxx>
  • Date: Tue, 6 Nov 2007 10:59:34 -0500
  • Delivery-date: Tue, 06 Nov 2007 08:00:16 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=oI32zz+P1Od0OXZ9dowZMX/gYT5yv62fRYQNoCsIBmNmlfTbwG37RPcOeFTn+k0mqkCkedV6MjFl+R9sAssaA+Hb2Yu2eg+yIht3BmzfFJLyhcyKEiZ2stYzVj9Xgeg/qVCsJGGZpS/5tc5ig13rZuSgdMzMJLE4ZGBTy9y2uSo=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Virsh (the xm-like tool that comes with libvirt) uses .xml files to
define and describe DomUs.  xm uses simple configuration files to
define and describe DomUs.  Is there any interoperability between
these two?  Like can virsh take an xm DomU config file, or vice versa?
 Or is there a tool to translate between them?

On a somewhat related note, can anyone tell me at a high level what is
different between the "vanilla" Xen source/distribution, and the Xen
source/distribution that comes with, for example, Fedora?  I know
Fedora includes libvirt when you choose "Virtualization" during
install, but I'm interested in changes made to the source by Fedora at
a lower level, for example:
 - Changes to the hypervisor itself
 - Changes to the paravirtualized kernel
 - Changes to various support files and scripts...for example all the
stuff in /etc/xen/scripts.


Xen-users mailing list



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