From 3afad0b2f08fe043adda4ee000786c501925883a Mon Sep 17 00:00:00 2001
From: Daniel Veillard
chmod 666 /var/run/xenstored/socket_ro
and also make sure that the Xen Daemon is running correctly
+and also make sure that the Xen Daemon is running correctly with local
+ HTTP server enabled, this is defined in
+ /etc/xen/xend-config.sxp
which need the following line to be
+ enabled:
(xend-http-server yes)
If needed restart the xend daemon after making the change with the + following command run as root:
+service xend restart
As most UNIX libraries libvir follows the "standard":
diff --git a/docs/Makefile.am b/docs/Makefile.am index c5d7808e3c..9518dfb9f6 100644 --- a/docs/Makefile.am +++ b/docs/Makefile.am @@ -14,7 +14,7 @@ EXTRA_DIST= \ man_MANS= -all: web $(man_MANS) +all: web $(top_builddir)/NEWS $(man_MANS) api: libvir-api.xml libvir-refs.xml $(APIPAGES) $(srcdir)/html/index.html @@ -49,6 +49,10 @@ $(srcdir)/html/index.html: libvir-api.xml $(srcdir)/newapi.xsl libvir-api.xml libvir-refs.xml: apibuild.py ../include/*.h ../src/*.h ../src/*.c -(./apibuild.py) +$(top_builddir)/NEWS: $(top_srcdir)/docs/news.xsl $(top_srcdir)/docs/news.html + -@(if [ -x $(XSLTPROC) ] ; then \ + $(XSLTPROC) --nonet $(top_srcdir)/docs/news.xsl $(top_srcdir)/docs/news.html > $(top_builddir)/NEWS ; fi ); + clean-local: rm -f *~ *.bak *.hierarchy *.signals *-unused.txt diff --git a/docs/architecture.html b/docs/architecture.html index 6bac95c226..dc0a91aa90 100644 --- a/docs/architecture.html +++ b/docs/architecture.html @@ -1,6 +1,7 @@ -When running in a Xen environment, programs using libvir have to execute +
When running in a Xen environment, programs using libvir have to execute in "Domain 0", which is the primary Linux OS loaded on the machine. That OS kernel provides most if not all of the actual drivers used by the set of domains. It also runs the Xen Store, a database of informations shared by the @@ -18,9 +19,9 @@ the Xen infrastructure:
If it runs without root access virConnectOpenReadOnly() should be used to +priviledge access).
If it runs without root access virConnectOpenReadOnly() should be used to
connect to initialize the library. It will try to open the read-only socket
/var/run/xenstored/socket_ro
to connect to the Xen Store and
also try to use the RPC to the Xen daemon. In this case use of hypervisor
calls and write to the Xen Store will not be possible, restraining the amount
-of APIs available and slowing down information gathering about domains.
Libvir is a C toolkit to interract with the virtualization capabilities of -recent versions of Linux (and other OSes), but ibvir won't try to provide all -possible interfaces for interacting with the virtualization features.
To avoid ambiguity about the terms used here here are the definitions for -soem of the specific terms used in libvir documentation:
Libvir is a C toolkit to interact with the virtualization capabilities of +recent versions of Linux (and other OSes), but libvir won't try to provide +all possible interfaces for interacting with the virtualization features.
To avoid ambiguity about the terms used here here are the definitions for +some of the specific concepts used in libvir documentation:
Now we can define the goal of libvir: to provide the lowest possible generic and stable layer to manage domains on a node.
This implies the following:
This implies the fol
So libvir should be a building block for higher level management tools or -for applications focusing on virtualization on a single node (the only +
So libvir should be a building block for higher level management tools and +for applications focusing on virtualization of a single node (the only exception being domain migration between node capabilities which may need to be added at the libvir level). Where possible libvir should be extendable to be able to provide the same API for remote nodes, however this is not the -case at the moment, the code currently handle only local node access.
Libvir is a C toolkit to interract with the virtualization capabilities of -recent versions of Linux (and other OSes), but ibvir won't try to provide all -possible interfaces for interacting with the virtualization features.
+Libvir is a C toolkit to interact with the virtualization capabilities of +recent versions of Linux (and other OSes), but libvir won't try to provide +all possible interfaces for interacting with the virtualization features.
To avoid ambiguity about the terms used here here are the definitions for -soem of the specific terms used in libvir documentation:
+some of the specific concepts used in libvir documentation:
virtualization framework
So libvir should be a building block for higher level management tools or -for applications focusing on virtualization on a single node (the only +
So libvir should be a building block for higher level management tools and +for applications focusing on virtualization of a single node (the only exception being domain migration between node capabilities which may need to be added at the libvir level). Where possible libvir should be extendable to be able to provide the same API for remote nodes, however this is not the -case at the moment, the code currently handle only local node access.
+case at the moment, the code currently handle only local node accesses.When running in a Xen environment, programs using libvir have to execute in "Domain 0", which is the primary Linux OS loaded on the machine. That OS kernel provides most if not all of the actual drivers used by the set of @@ -113,14 +127,14 @@ the Xen infrastructure:
changing the state of the system, but for performance and accuracy reasons may talk directly to the hypervisor when gathering state informations at least when possible (i.e. when the running program using libvir has root -priviledge access). +priviledge access). -If it runs without root access virConnectOpenReadOnly() should be used to +
If it runs without root access virConnectOpenReadOnly() should be used to
connect to initialize the library. It will try to open the read-only socket
/var/run/xenstored/socket_ro
to connect to the Xen Store and
also try to use the RPC to the Xen daemon. In this case use of hypervisor
calls and write to the Xen Store will not be possible, restraining the amount
-of APIs available and slowing down information gathering about domains.
chmod 666 /var/run/xenstored/socket_ro
and also make sure that the Xen Daemon is running correctly
+and also make sure that the Xen Daemon is running correctly with local
+ HTTP server enabled, this is defined in
+ /etc/xen/xend-config.sxp
which need the following line to be
+ enabled:
(xend-http-server yes)
If needed restart the xend daemon after making the change with the + following command run as root:
+service xend restart
Here is the list of official releases, however since it is early on in the development of libvir, it is preferable when possible to just use the CVS version or snapshot, contact the mailing list -and check the ChangeLog to gauge progresses.