Index: virsh.1
===================================================================
RCS file: /data/cvs/libvirt/virsh.1,v
retrieving revision 1.11
diff -u -r1.11 virsh.1
--- virsh.1 5 Feb 2008 19:27:37 -0000 1.11
+++ virsh.1 14 Mar 2008 10:06:33 -0000
@@ -241,7 +241,7 @@
for each kind of guest which can be virtualized. For a more complete
description see:
-The \s-1XML\s0 also show the \s-1NUMA\s0 topology informations if available.
+The \s-1XML\s0 also show the \s-1NUMA\s0 topology information if available.
.IP "\fBlist\fR" 4
.IX Item "list"
Prints information about one or more domains. If no domains are
@@ -353,7 +353,7 @@
Returns state about a running domain.
.IP "\fBdumpxml\fR \fIdomain-id\fR" 4
.IX Item "dumpxml domain-id"
-Output the domain informations as an \s-1XML\s0 dump to stdout, this format can be used by the \fBcreate\fR command.
+Output the domain information as an \s-1XML\s0 dump to stdout, this format can be used by the \fBcreate\fR command.
.IP "\fBreboot\fR \fIdomain-id\fR" 4
.IX Item "reboot domain-id"
Reboot a domain. This acts just as if the domain had the \fBreboot\fR
@@ -480,7 +480,7 @@
.IX Header "VIRTUAL NETWORKS COMMANDS"
The following commands manipulate networks. Libvirt has the capability to
define virtual networks which can then be used by domains and linked to
-actual network devices. For more detailed informations about this feature
+actual network devices. For more detailed information about this feature
see the documentation at . A lot
of the command for virtual networks are similar to the one used for domains,
but the way to name a virtual network is either by its name or \s-1UUID\s0.
Index: docs/apibuild.py
===================================================================
RCS file: /data/cvs/libvirt/docs/apibuild.py,v
retrieving revision 1.23
diff -u -r1.23 apibuild.py
--- docs/apibuild.py 5 Feb 2008 19:27:37 -0000 1.23
+++ docs/apibuild.py 14 Mar 2008 10:06:33 -0000
@@ -752,7 +752,7 @@
return((args, desc))
#
- # Parse a comment block and merge the informations found in the
+ # Parse a comment block and merge the information found in the
# parameters descriptions, finally returns a block as complete
# as possible
#
Index: docs/architecture.html
===================================================================
RCS file: /data/cvs/libvirt/docs/architecture.html,v
retrieving revision 1.41
diff -u -r1.41 architecture.html
--- docs/architecture.html 20 Feb 2008 15:58:06 -0000 1.41
+++ docs/architecture.html 14 Mar 2008 10:06:34 -0000
@@ -8,7 +8,7 @@
When running in a Xen environment, programs using libvirt 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
+domains. It also runs the Xen Store, a database of information shared by the
hypervisor, the kernels, the drivers and the xen daemon. Xend. The xen daemon
supervise the control and execution of the sets of domains. The hypervisor,
drivers, kernels and daemons communicate though a shared system bus
@@ -23,7 +23,7 @@
as root and providing read-only support
The library will usually interact with the Xen daemon for any operation
changing the state of the system, but for performance and accuracy reasons
-may talk directly to the hypervisor when gathering state informations at
+may talk directly to the hypervisor when gathering state information at
least when possible (i.e. when the running program using libvirt has root
priviledge access).
If it runs without root access virConnectOpenReadOnly() should be used to
connect to initialize the library. It will then fork a libvirt_proxy
Index: docs/errors.html
===================================================================
RCS file: /data/cvs/libvirt/docs/errors.html,v
retrieving revision 1.24
diff -u -r1.24 errors.html
--- docs/errors.html 3 Mar 2008 14:42:37 -0000 1.24
+++ docs/errors.html 14 Mar 2008 10:06:34 -0000
@@ -1,7 +1,7 @@
Handling of errors
Handling of errors
The main goals of libvirt when it comes to error handling are:
provide as much detail as possible
-
provide the informations as soon as possible
+
provide the information as soon as possible
dont force the library user into one style of error handling
As result the library provide both synchronous, callback based and
asynchronous error reporting. When an error happens in the library code the
@@ -15,7 +15,7 @@
set specifically to a connection with
So error handling in the code is the following:
if the error can be associated to a connection for example when failing
to look up a domain
if there is a callback associated to the connection set with virConnSetErrorFunc,
- call it with the error informations
+ call it with the error information
otherwise if there is a global callback set with virSetErrorFunc,
call it with the error information
@@ -44,10 +44,10 @@
connection to the hypervisor where this happened
dom: if available a pointer to the virDomainPtr domain
targetted in the operation
-
and then extra raw informations about the error which may be initialized
-to 0 or NULL if unused
str1, str2, str3: string informations, usually str1 is the error
+
and then extra raw information about the error which may be initialized
+to 0 or NULL if unused
str1, str2, str3: string information, usually str1 is the error
message format
-
int1, int2: integer informations
+
int1, int2: integer information
So usually, setting up specific error handling with libvirt consist of
registering an handler with with virSetErrorFunc or
with virConnSetErrorFunc,
Index: docs/format.html
===================================================================
RCS file: /data/cvs/libvirt/docs/format.html,v
retrieving revision 1.37
diff -u -r1.37 format.html
--- docs/format.html 3 Mar 2008 14:42:37 -0000 1.37
+++ docs/format.html 14 Mar 2008 10:06:34 -0000
@@ -157,7 +157,7 @@
the <os> block description is very different, first
it indicates that the type is 'hvm' for hardware virtualization, then
instead of a kernel, boot and command line arguments, it points to an os
- boot loader which will extract the boot informations from the boot device
+ boot loader which will extract the boot information from the boot device
specified in a separate boot element. The dev attribute on
the boot tag can be one of:
fd - boot from first floppy device
@@ -415,7 +415,7 @@
block is similar to what you will find in a Xen fully virtualized domain
description).
The second block (in blue) indicates the paravirtualization support of the
Xen support, you will see the os_type of xen to indicate a paravirtual
-kernel, then architecture informations and potential features.
The third block (in green) gives similar informations but when running a
+kernel, then architecture information and potential features.
The third block (in green) gives similar information but when running a
32 bit OS fully virtualized with Xen using the hvm support.
This section is likely to be updated and augmented in the future, see the
discussion which led to the capabilities format in the mailing-list
archives.
Index: docs/index.py
===================================================================
RCS file: /data/cvs/libvirt/docs/index.py,v
retrieving revision 1.3
diff -u -r1.3 index.py
--- docs/index.py 5 Feb 2008 19:27:37 -0000 1.3
+++ docs/index.py 14 Mar 2008 10:06:35 -0000
@@ -34,7 +34,7 @@
# Bye
#
# Then run the script in the doc subdir, it will create the symbols and
-# word tables and populate them with informations extracted from
+# word tables and populate them with information extracted from
# the libvirt-api.xml API description, and make then accessible read-only
# by nobody@loaclhost the user expected to be Apache's one
#
Index: docs/libvir.html
===================================================================
RCS file: /data/cvs/libvirt/docs/libvir.html,v
retrieving revision 1.110
diff -u -r1.110 libvir.html
--- docs/libvir.html 7 Mar 2008 11:13:02 -0000 1.110
+++ docs/libvir.html 14 Mar 2008 10:06:41 -0000
@@ -254,7 +254,7 @@
Documentation: remote support (Richard Jones), description of
the URI connection strings (Richard Jones), update of virsh man
page, matrix of libvirt API/hypervisor support with version
- informations (Richard Jones)
+ information (Richard Jones)
Bug fixes: examples Makefile.am generation (Richard Jones),
SetMem fix (Mark Johnson), URI handling and ordering of
drivers (Daniel Berrange), fix virsh help without hypervisor (Richard
@@ -424,7 +424,7 @@
0.1.9: Nov 29 2006
python bindings: release interpeter lock when calling C (Daniel Berrange)
-
don't raise HTTP error when looking informations for a domain
+
don't raise HTTP error when looking information for a domain
some refactoring to use the driver for all entry points
better error reporting (Daniel Berrange)
fix OS reporting when running as non-root
@@ -442,7 +442,7 @@
added support for inactive domains, new APIs, various associated cleanup (Daniel Berrange)
special device model for HVM guests (Daniel Berrange)
add API to dump core of domains (but requires a patched xend)
-
pygrub bootloader informations take over <os> informations
+
pygrub bootloader information take over <os> information
updated the localization strings
0.1.8: Oct 16 2006
@@ -459,9 +459,9 @@
0.1.7: Sep 29 2006
-
fix a memory bug on getting vcpu informations from xend (Daniel Berrange)
+
fix a memory bug on getting vcpu information from xend (Daniel Berrange)
fix another problem in the hypercalls change in Xen changeset
- 86d26e6ec89b when getting domain informations (Daniel Berrange)
+ 86d26e6ec89b when getting domain information (Daniel Berrange)
improvements: UUID in XML description (Peter Vetere), proxy code
cleanup, virtual CPU and affinity support + virsh support (Michel
- Ponceau, Philippe Berthault, Daniel Berrange), port and tty informations
+ Ponceau, Philippe Berthault, Daniel Berrange), port and tty information
for console in XML (Daniel Berrange), added XML dump to driver and proxy
support (Daniel Berrange), extention of boot options with support for
floppy and cdrom (Daniel Berrange), features block in XML to report/ask
@@ -678,7 +678,7 @@
When running in a Xen environment, programs using libvirt 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
+domains. It also runs the Xen Store, a database of information shared by the
hypervisor, the kernels, the drivers and the xen daemon. Xend. The xen daemon
supervise the control and execution of the sets of domains. The hypervisor,
drivers, kernels and daemons communicate though a shared system bus
@@ -700,7 +700,7 @@
The library will usually interact with the Xen daemon for any operation
changing the state of the system, but for performance and accuracy reasons
-may talk directly to the hypervisor when gathering state informations at
+may talk directly to the hypervisor when gathering state information at
least when possible (i.e. when the running program using libvirt has root
priviledge access).
@@ -995,7 +995,7 @@
the <os> block description is very different, first
it indicates that the type is 'hvm' for hardware virtualization, then
instead of a kernel, boot and command line arguments, it points to an os
- boot loader which will extract the boot informations from the boot device
+ boot loader which will extract the boot information from the boot device
specified in a separate boot element. The dev attribute on
the boot tag can be one of:
@@ -1300,9 +1300,9 @@
The second block (in blue) indicates the paravirtualization support of the
Xen support, you will see the os_type of xen to indicate a paravirtual
-kernel, then architecture informations and potential features.
+kernel, then architecture information and potential features.
-
The third block (in green) gives similar informations but when running a
+
The third block (in green) gives similar information but when running a
32 bit OS fully virtualized with Xen using the hvm support.
This section is likely to be updated and augmented in the future, see
Documentation: remote support (Richard Jones), description of
the URI connection strings (Richard Jones), update of virsh man
page, matrix of libvirt API/hypervisor support with version
- informations (Richard Jones)
+ information (Richard Jones)
Bug fixes: examples Makefile.am generation (Richard Jones),
SetMem fix (Mark Johnson), URI handling and ordering of
drivers (Daniel Berrange), fix virsh help without hypervisor (Richard
@@ -344,7 +344,7 @@
bug fixes: VCPU info breakages on xen 3.0.3, xenDaemonListDomains buffer overflow (Daniel Berrange), reference count bug when creating Xen domains (Daniel Berrange).
improvements: support graphic framebuffer for Xen paravirt (Daniel Berrange), VNC listen IP range support (Daniel Berrange), support for default Xen config files and inactive domains of 3.0.4 (Daniel Berrange).
0.1.9: Nov 29 2006
python bindings: release interpeter lock when calling C (Daniel Berrange)
-
don't raise HTTP error when looking informations for a domain
+
don't raise HTTP error when looking information for a domain
some refactoring to use the driver for all entry points
better error reporting (Daniel Berrange)
fix OS reporting when running as non-root
@@ -362,7 +362,7 @@
added support for inactive domains, new APIs, various associated cleanup (Daniel Berrange)
special device model for HVM guests (Daniel Berrange)
add API to dump core of domains (but requires a patched xend)
-
pygrub bootloader informations take over <os> informations
+
pygrub bootloader information take over <os> information
updated the localization strings
0.1.8: Oct 16 2006
Bug for system with page size != 4k
vcpu number initialization (Philippe Berthault)
@@ -373,9 +373,9 @@
compile fix
mlock/munlock size fixes (Daniel Berrange)
improve error reporting
-
0.1.7: Sep 29 2006
fix a memory bug on getting vcpu informations from xend (Daniel Berrange)
+
0.1.7: Sep 29 2006
fix a memory bug on getting vcpu information from xend (Daniel Berrange)
fix another problem in the hypercalls change in Xen changeset
- 86d26e6ec89b when getting domain informations (Daniel Berrange)
+ 86d26e6ec89b when getting domain information (Daniel Berrange)
0.1.6: Sep 22 2006
Support for localization of strings using gettext (Daniel Berrange)
Support for new Xen-3.0.3 cdrom and disk configuration (Daniel Berrange)
Support for setting VNC port when creating domains with new
@@ -401,7 +401,7 @@
initialization errors (Daniel Berrange)
improvements: UUID in XML description (Peter Vetere), proxy code
cleanup, virtual CPU and affinity support + virsh support (Michel
- Ponceau, Philippe Berthault, Daniel Berrange), port and tty informations
+ Ponceau, Philippe Berthault, Daniel Berrange), port and tty information
for console in XML (Daniel Berrange), added XML dump to driver and proxy
support (Daniel Berrange), extention of boot options with support for
floppy and cdrom (Daniel Berrange), features block in XML to report/ask
Index: docs/python.html
===================================================================
RCS file: /data/cvs/libvirt/docs/python.html,v
retrieving revision 1.24
diff -u -r1.24 python.html
--- docs/python.html 3 Mar 2008 14:42:37 -0000 1.24
+++ docs/python.html 14 Mar 2008 10:06:49 -0000
@@ -5,7 +5,7 @@
allow direct acces from C++ code, but also we have bindings for
higher level kind of languages:
Python: Libvirt comes with direct support for the Python language
(just make sure you installed the libvirt-python package if not
- compiling from sources). See below for more informations about
+ compiling from sources). See below for more information about
using libvirt with python
Support, requests or help for libvirt bindings are welcome on
the mailing
-list, as usual try to provide enough background informations
+list, as usual try to provide enough background information
and make sure you use recent version, see the help
page.
The remaining of this page focuses on the Python bindings.
The Python binding should be complete and are mostly automatically
generated from the formal description of the API in xml. The bindings are
@@ -59,7 +59,7 @@
openReadOnly function allows the code to execute as a normal user.
getting an object representing the Domain 0 using lookupByName
if the domain is not found a libvirtError exception will be raised
-
extracting and printing some informations about the domain using
+
extracting and printing some information about the domain using
various methods
associated to the virDomain class.