libvirt/examples/python
Daniel P. Berrange 6b3ede3f02 Remove bogus check for Xen in example program
The dominfo.py example script has a bogus check for /proc/xen
existing. The default connection cannot be assumed to be Xen
any more

* examples/python/dominfo.py: Remove check for Xen
2010-11-29 15:17:00 +00:00
..
dominfo.py Remove bogus check for Xen in example program 2010-11-29 15:17:00 +00:00
domrestore.py Use python discovered through env instead of hardcoding a path 2010-11-14 22:45:59 +01:00
domsave.py Use python discovered through env instead of hardcoding a path 2010-11-14 22:45:59 +01:00
domstart.py Use python discovered through env instead of hardcoding a path 2010-11-14 22:45:59 +01:00
esxlist.py Use python discovered through env instead of hardcoding a path 2010-11-14 22:45:59 +01:00
Makefile.am
README

Some simple examples on how to use the Python API for libvirt

The examples are:

dominfo.py  - print information about a running domU based on the results of
              virDomainGetInfo and virDomainGetXMLDesc
domstart.py - create a domU from an XML description if the domU isn't
              running yet
domsave.py  - save all running domU's into a directory
domrestore.py - restore domU's from their saved files in a directory
esxlist.py  - list active domains of an VMware ESX host and print some info.
              also demonstrates how to use the libvirt.openAuth() method

The XML files in this directory are examples of the XML format that libvirt
expects, and will have to be adapted for your setup. They are only needed
for domstart.py


Some additional notes for the esxlist.py example:

You may see remote errors complaining about missing certificates:

  Cannot access CA certificate '/usr/local/etc/pki/CA/cacert.pem': No such file
  or directory

This is expected, libvirt tries to find network and storage drivers for ESX,
but those are not implemented yet (November 2009). While searching for this
drivers, libvirt may try to start a local libvirtd instance, but fails because
of the missing certificates. It'll warn about that:

  Failed to find the network: Is the daemon running?

This is also expected and can be ignored.