Release of 0.4.1

* NEWS configure.in libvirt.spec.in docs/* include/libvirt/libvirt.h
  po/*: preparing release of libvirt-0.4.1
Daniel

ChangeLog

@@ -1,3 +1,8 @@
+Mon Mar  3 15:40:31 CET 2008 Daniel Veillard <veillard@redhat.com>
+
+	* NEWS configure.in libvirt.spec.in docs/* include/libvirt/libvirt.h
+	  po/*: preparing release of libvirt-0.4.1
+
 Mon Mar  3 14:14:03 CET 2008 Jim Meyering <meyering@redhat.com>
 
 	Plug saslUsernameWhitelist leak.

NEWS

@@ -5,12 +5,66 @@
        http://libvirt.org/news.html
 
 Releases
+0.4.1: Mar 3 2008:
+   - New features: build on MacOSX (Richard Jones), storage management
+      (Daniel Berrange), Xenner - Xen on KVM - support (Daniel Berrange)
+   - Documentation: Fix of various typos (Atsushi SAKAI), memory and
+      vcpu settings details (Richard Jones), ethernet bridging typo
+      (Maxwell Bottiger), add storage APIs documentation (Daniel Berrange)
+   - Bug fixes: OpenVZ code compilation (Mikhail Pokidko), crash in
+      policykit auth handling (Daniel Berrange), large config files
+      (Daniel Berrange), cpumap hypercall size (Saori Fukuta), crash
+      in remote auth (Daniel Berrange), ssh args error (Daniel Berrange),
+      preserve vif order from config files (Hiroyuki Kaguchi), invalid
+      pointer access (Jim Meyering), virDomainGetXMLDesc flag handling,
+      device name conversion on stats (Daniel Berrange), double mutex lock
+      (Daniel Berrange), config file reading crashes (Guido Guenther),
+      xenUnifiedDomainSuspend bug (Marcus Meissner), do not crash if
+      /sys/hypervisor/capabilities is missing (Mark McLoughlin),
+      virHashRemoveSet bug (Hiroyuki Kaguchi), close-on-exec flag for
+      qemud signal pipe (Daniel Berrange), double free in OpenVZ
+      (Anton Protopopov), handle mac without addresses (Shigeki Sakamoto),
+      MAC addresses checks (Shigeki Sakamoto and Richard Jones)
+   - Improvements: Windows build (Richard Jones), KVM/QEmu shutdown
+      (Guido Guenther), catch virExec output on debug (Mark McLoughlin),
+      integration of iptables and lokkit (Mark McLoughlin), keymap
+      parameter for VNC servers (Daniel Hokka Zakrisson), enable debug
+      by default using VIR_DEBUG (Daniel Berrange), xen 3.2 fixes
+      (Daniel Berrange), Python bindings for VCPU and scheduling
+      (Daniel Berrange), framework for automatic code syntax checks
+      (Jim Meyering), allow kernel+initrd setup in Xen PV (Daniel Berrange),
+      allow change of Disk/NIC of an inactive domains (Shigeki Sakamoto),
+      virsh commands to manipulate and create storage(Daniel Berrange),
+      update use of PolicyKit APIs, better detection of fedault hypervisor,
+      block device statistics for QEmu/KVM (Richard Jones), various improvements
+      for Xenner (Daniel Berrange)
+   - Code cleanups: avoid warnings (Daniel Berrange), virRun helper
+      function (Dan Berrange), iptable code fixes (Mark McLoughlin),
+      static and const cleanups (Jim Meyering), malloc and python cleanups
+      (Jim Meyering), xstrtol_ull and xstrtol_ll functions (Daniel Berrange),
+      remove no-op networking from OpenVZ (Daniel Berrange), python generator
+      cleanups (Daniel Berrange), cleanup ref counting (Daniel Berrange),
+      remove uninitialized warnings (Jim Meyering), cleanup configure
+      for RHEL4 (Daniel Berrange), CR/LF cleanups (Richard Jones),
+      various automatic code check and associated cleanups (Jim Meyering),
+      various memory leaks (Jim Meyering), fix compilation when building
+      without Xen (Guido Guenther), mark translatables strings (Jim Meyering),
+      use virBufferAddLit for constant strings (Jim Meyering), fix
+      make distcheck (Jim Meyering), return values for python bindings (Cole
+      Robinson), trailing blanks fixes (Jim Meyering), gcc-4.3.0 fixes
+      (Mark McLoughlin), use safe read and write routines (Jim Meyering),
+      refactoring of code dealing with hypervisor capabilities (Daniel
+      Berrange), qemudReportError to use virErrorMsg (Cole Robinson),
+      intemediate library and Makefiles for compiling static and coverage
+      rule support (Jim Meyering), cleanup of various leaks (Jim Meyering)
+
+
 0.4.0: Dec 18 2007:
    - New features: Compilation on Windows cygwin/mingw (Richard Jones),
       Ruby bindings (David Lutterkort), SASL based authentication for
       libvirt remote support (Daniel Berrange), PolicyKit authentication
       (Daniel Berrange)
-   - Documentation: example files for QEMU and libvirtd configurations
+   - Documentation: example files for QEMU and libvirtd configuations
       (Daniel Berrange), english cleanups (Jim Paris), CIM and OpenVZ
       references, document <shareable/>, daemon startup when using
       QEMU/KVM, document HV support for new NUMA calls (Richard Jones),

configure.in

@@ -1,6 +1,6 @@
 dnl Process this file with autoconf to produce a configure script.
 
-AC_INIT(libvirt, 0.4.0)
+AC_INIT(libvirt, 0.4.1)
 AC_CONFIG_SRCDIR(src/libvirt.c)
 AC_CONFIG_AUX_DIR(build-aux)
 AM_CONFIG_HEADER(config.h)

docs/errors.html

@@ -8,7 +8,7 @@ asynchronous error reporting. When an error happens in the library code the
 error is logged, allowing to retrieve it later and if the user registered an
 error callback it will be called synchronously. Once the call to libvirt ends
 the error can be detected by the return value and the full information for
-the last logged error can be retrieved.</p><p>To avoid as much as possible troubles with a global variable in a
+the last logged error can be retrieved.</p><p>To avoid as much as prossible troubles with a global variable in a
 multithreaded environment, libvirt will associate when possible the errors to
 the current connection they are related to, that way the error is stored in a
 dynamic structure which can be made thread specific. Error callback can be
@@ -43,7 +43,7 @@ following fields:</p><ul><li>code: an error number from the <a href="html/libvir
   <li>conn: if available a pointer to the <a href="html/libvirt-libvirt.html#virConnectPtr">virConnectPtr</a>
     connection to the hypervisor where this happened</li>
   <li>dom: if available a pointer to the <a href="html/libvirt-libvirt.html#virDomainPtr">virDomainPtr</a> domain
-    targeted in the operation</li>
+    targetted in the operation</li>
 </ul><p>and then extra raw informations about the error which may be initialized
 to 0 or NULL if unused</p><ul><li>str1, str2, str3: string informations, usually str1 is the error
     message format</li>
@@ -51,7 +51,7 @@ to 0 or NULL if unused</p><ul><li>str1, str2, str3: string informations, usually
 </ul><p>So usually, setting up specific error handling with libvirt consist of
 registering an handler with with <a href="html/libvirt-virterror.html#virSetErrorFunc">virSetErrorFunc</a> or
 with <a href="html/libvirt-virterror.html#virConnSetErrorFunc">virConnSetErrorFunc</a>,
-check the value of the code value, take appropriate action, if needed let
+chech the value of the code value, take appropriate action, if needed let
 libvirt print the error on stderr by calling <a href="html/libvirt-virterror.html#virDefaultErrorFunc">virDefaultErrorFunc</a>.
 For asynchronous error handing, set such a function doing nothing to avoid
 the error being reported on stderr, and call virConnGetLastError or

docs/format.html

@@ -45,7 +45,7 @@ significant:</p><ul><li>name: the domain name, preferably ASCII based</li>
   <li>memory: the maximum memory allocated to the domain in kilobytes</li>
   <li>vcpu: the number of virtual cpu configured for the domain</li>
   <li>os: a block describing the Operating System, its content will be
-    dependent on the OS type
+    dependant on the OS type
     <ul><li>type: indicate the OS type, always linux at this point</li>
       <li>kernel: path to the kernel on the Domain 0 filesystem</li>
       <li>initrd: an optional path for the init ramdisk on the Domain 0
@@ -168,7 +168,7 @@ systems:</p><pre>&lt;domain type='xen' id='3'&gt;
     pointing to an additional program in charge of emulating the devices</li>
   <li>the disk entry indicates in the dev target section that the emulation
     for the drive is the first IDE disk device hda. The list of device names
-    supported is dependent on the Hypervisor, but for Xen it can be any IDE
+    supported is dependant on the Hypervisor, but for Xen it can be any IDE
     device <code>hda</code>-<code>hdd</code>, or a floppy device
     <code>fda</code>, <code>fdb</code>. The <code>&lt;disk&gt;</code> element
     also supports a 'device' attribute to indicate what kinda of hardware to
@@ -247,7 +247,7 @@ support a variety of options:</p><ol><li>Userspace SLIRP stack
     of the box which does NAT'ing to the default route and has an IP range of
     <code>192.168.22.0/255.255.255.0</code>. Each guest will have an
     associated tun device created with a name of vnetN, which can also be
-    overridden with the &lt;target&gt; element. Example configs are:</p>
+    overriden with the &lt;target&gt; element. Example configs are:</p>
     <pre>&lt;interface type='network'&gt;
   &lt;source network='default'/&gt;
 &lt;/interface&gt;
@@ -263,7 +263,7 @@ support a variety of options:</p><ol><li>Userspace SLIRP stack
     <p>Provides a bridge from the VM directly onto the LAN. This assumes
     there is a bridge device on the host which has one or more of the hosts
     physical NICs enslaved. The guest VM will have an associated tun device
-    created with a name of vnetN, which can also be overridden with the
+    created with a name of vnetN, which can also be overriden with the
     &lt;target&gt; element. The tun device will be enslaved to the bridge.
     The IP range / network configuration is whatever is used on the LAN. This
     provides the guest VM full incoming &amp; outgoing net access just like a
@@ -281,11 +281,11 @@ support a variety of options:</p><ol><li>Userspace SLIRP stack
   <li>Generic connection to LAN
     <p>Provides a means for the administrator to execute an arbitrary script
     to connect the guest's network to the LAN. The guest will have a tun
-    device created with a name of vnetN, which can also be overridden with the
+    device created with a name of vnetN, which can also be overriden with the
     &lt;target&gt; element. After creating the tun device a shell script will
     be run which is expected to do whatever host network integration is
     required. By default this script is called /etc/qemu-ifup but can be
-    overridden.</p>
+    overriden.</p>
     <pre>&lt;interface type='ethernet'/&gt;
 
 &lt;interface type='ethernet'&gt;
@@ -409,7 +409,7 @@ BIOS you will see</p><pre>&lt;capabilities&gt;
     &lt;/features&gt;
   &lt;/guest&gt;</span>
   ...
-&lt;/capabilities&gt;</pre><p>The first block (in red) indicates the host hardware capabilities, currently
+&lt;/capabilities&gt;</pre><p>The first block (in red) indicates the host hardware capbilities, currently
 it is limited to the CPU properties but other information may be available,
 it shows the CPU architecture, and the features of the chip (the feature
 block is similar to what you will find in a Xen fully virtualized domain

docs/index.html

@@ -20,7 +20,7 @@ of recent versions of Linux (and other OSes). It is free software available
 under the <a href="http://www.opensource.org/licenses/lgpl-license.html">GNU
 Lesser General Public License</a>. Virtualization of the Linux Operating
 System means the ability to run multiple instances of Operating Systems
-concurrently on a single hardware system where the basic resources are driven
+concurently on a single hardware system where the basic resources are driven
 by a Linux (or Solaris) instance. The library aims at providing a long term
 stable C API initially for <a href="http://www.cl.cam.ac.uk/Research/SRG/netos/xen/index.html">Xen
 paravirtualization</a> but it can also integrate with other

docs/libvir.html

@@ -37,6 +37,61 @@ href="downloads.html">CVS version or snapshot</a>, contact the mailing list
 and check the <a href="ChangeLog.html">ChangeLog</a> to gauge progress.</p>
 
 
+<h3>0.4.1: Mar 3 2008</h3>
+<ul>
+  <li>New features: build on MacOSX (Richard Jones), storage management
+      (Daniel Berrange), Xenner - Xen on KVM - support (Daniel Berrange)</li>
+  <li>Documentation: Fix of various typos (Atsushi SAKAI), memory and
+      vcpu settings details (Richard Jones), ethernet bridging typo
+      (Maxwell Bottiger), add storage APIs documentation (Daniel Berrange)</li>
+  <li>Bug fixes: OpenVZ code compilation (Mikhail Pokidko), crash in
+      policykit auth handling (Daniel Berrange), large config files
+      (Daniel Berrange), cpumap hypercall size (Saori Fukuta), crash
+      in remote auth (Daniel Berrange), ssh args error (Daniel Berrange),
+      preserve vif order from config files (Hiroyuki Kaguchi), invalid
+      pointer access (Jim Meyering), virDomainGetXMLDesc flag handling,
+      device name conversion on stats (Daniel Berrange), double mutex lock
+      (Daniel Berrange), config file reading crashes (Guido Guenther),
+      xenUnifiedDomainSuspend bug (Marcus Meissner), do not crash if
+      /sys/hypervisor/capabilities is missing (Mark McLoughlin),
+      virHashRemoveSet bug (Hiroyuki Kaguchi), close-on-exec flag for
+      qemud signal pipe (Daniel Berrange), double free in OpenVZ
+      (Anton Protopopov), handle mac without addresses (Shigeki Sakamoto),
+      MAC addresses checks (Shigeki Sakamoto and Richard Jones)</li>
+  <li>Improvements: Windows build (Richard Jones), KVM/QEmu shutdown
+      (Guido Guenther), catch virExec output on debug (Mark McLoughlin),
+      integration of iptables and lokkit (Mark McLoughlin), keymap
+      parameter for VNC servers (Daniel Hokka Zakrisson), enable debug
+      by default using VIR_DEBUG (Daniel Berrange), xen 3.2 fixes
+      (Daniel Berrange), Python bindings for VCPU and scheduling
+      (Daniel Berrange), framework for automatic code syntax checks
+      (Jim Meyering), allow kernel+initrd setup in Xen PV (Daniel Berrange),
+      allow change of Disk/NIC of an inactive domains (Shigeki Sakamoto),
+      virsh commands to manipulate and create storage(Daniel Berrange),
+      update use of PolicyKit APIs, better detection of fedault hypervisor,
+      block device statistics for QEmu/KVM (Richard Jones), various improvements
+      for Xenner (Daniel Berrange)</li>
+  <li>Code cleanups: avoid warnings (Daniel Berrange), virRun helper
+      function (Dan Berrange), iptable code fixes (Mark McLoughlin),
+      static and const cleanups (Jim Meyering), malloc and python cleanups
+      (Jim Meyering), xstrtol_ull and xstrtol_ll functions (Daniel Berrange),
+      remove no-op networking from OpenVZ (Daniel Berrange), python generator
+      cleanups (Daniel Berrange), cleanup ref counting (Daniel Berrange),
+      remove uninitialized warnings (Jim Meyering), cleanup configure
+      for RHEL4 (Daniel Berrange), CR/LF cleanups (Richard Jones),
+      various automatic code check and associated cleanups (Jim Meyering),
+      various memory leaks (Jim Meyering), fix compilation when building
+      without Xen (Guido Guenther), mark translatables strings (Jim Meyering),
+      use virBufferAddLit for constant strings (Jim Meyering), fix
+      make distcheck (Jim Meyering), return values for python bindings (Cole
+      Robinson), trailing blanks fixes (Jim Meyering), gcc-4.3.0 fixes
+      (Mark McLoughlin), use safe read and write routines (Jim Meyering),
+      refactoring of code dealing with hypervisor capabilities (Daniel
+      Berrange), qemudReportError to use virErrorMsg (Cole Robinson),
+      intemediate library and Makefiles for compiling static and coverage
+      rule support (Jim Meyering), cleanup of various leaks (Jim Meyering)</li>
+</ul>
+
 <h3>0.4.0: Dec 18 2007</h3>
 <ul>
   <li>New features: Compilation on Windows cygwin/mingw (Richard Jones),

docs/news.html

@@ -2,11 +2,62 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /><link rel="stylesheet" type="text/css" href="libvirt.css" /><link rel="SHORTCUT ICON" href="/32favicon.png" /><title>Releases</title></head><body><div id="container"><div id="intro"><div id="adjustments"></div><div id="pageHeader"></div><div id="content2"><h1 class="style1">Releases</h1><p>Here is the list of official releases, however since it is early on in the
 development of libvirt, it is preferable when possible to just use the <a href="downloads.html">CVS version or snapshot</a>, contact the mailing list
-and check the <a href="ChangeLog.html">ChangeLog</a> to gauge progress.</p><h3>0.4.0: Dec 18 2007</h3><ul><li>New features: Compilation on Windows cygwin/mingw (Richard Jones),
+and check the <a href="ChangeLog.html">ChangeLog</a> to gauge progress.</p><h3>0.4.1: Mar 3 2008</h3><ul><li>New features: build on MacOSX (Richard Jones), storage management
+      (Daniel Berrange), Xenner - Xen on KVM - support (Daniel Berrange)</li>
+  <li>Documentation: Fix of various typos (Atsushi SAKAI), memory and
+      vcpu settings details (Richard Jones), ethernet bridging typo
+      (Maxwell Bottiger), add storage APIs documentation (Daniel Berrange)</li>
+  <li>Bug fixes: OpenVZ code compilation (Mikhail Pokidko), crash in
+      policykit auth handling (Daniel Berrange), large config files
+      (Daniel Berrange), cpumap hypercall size (Saori Fukuta), crash
+      in remote auth (Daniel Berrange), ssh args error (Daniel Berrange),
+      preserve vif order from config files (Hiroyuki Kaguchi), invalid
+      pointer access (Jim Meyering), virDomainGetXMLDesc flag handling,
+      device name conversion on stats (Daniel Berrange), double mutex lock
+      (Daniel Berrange), config file reading crashes (Guido Guenther),
+      xenUnifiedDomainSuspend bug (Marcus Meissner), do not crash if
+      /sys/hypervisor/capabilities is missing (Mark McLoughlin),
+      virHashRemoveSet bug (Hiroyuki Kaguchi), close-on-exec flag for
+      qemud signal pipe (Daniel Berrange), double free in OpenVZ
+      (Anton Protopopov), handle mac without addresses (Shigeki Sakamoto),
+      MAC addresses checks (Shigeki Sakamoto and Richard Jones)</li>
+  <li>Improvements: Windows build (Richard Jones), KVM/QEmu shutdown
+      (Guido Guenther), catch virExec output on debug (Mark McLoughlin),
+      integration of iptables and lokkit (Mark McLoughlin), keymap
+      parameter for VNC servers (Daniel Hokka Zakrisson), enable debug
+      by default using VIR_DEBUG (Daniel Berrange), xen 3.2 fixes
+      (Daniel Berrange), Python bindings for VCPU and scheduling
+      (Daniel Berrange), framework for automatic code syntax checks
+      (Jim Meyering), allow kernel+initrd setup in Xen PV (Daniel Berrange),
+      allow change of Disk/NIC of an inactive domains (Shigeki Sakamoto),
+      virsh commands to manipulate and create storage(Daniel Berrange),
+      update use of PolicyKit APIs, better detection of fedault hypervisor,
+      block device statistics for QEmu/KVM (Richard Jones), various improvements
+      for Xenner (Daniel Berrange)</li>
+  <li>Code cleanups: avoid warnings (Daniel Berrange), virRun helper
+      function (Dan Berrange), iptable code fixes (Mark McLoughlin),
+      static and const cleanups (Jim Meyering), malloc and python cleanups
+      (Jim Meyering), xstrtol_ull and xstrtol_ll functions (Daniel Berrange),
+      remove no-op networking from OpenVZ (Daniel Berrange), python generator
+      cleanups (Daniel Berrange), cleanup ref counting (Daniel Berrange),
+      remove uninitialized warnings (Jim Meyering), cleanup configure
+      for RHEL4 (Daniel Berrange), CR/LF cleanups (Richard Jones),
+      various automatic code check and associated cleanups (Jim Meyering),
+      various memory leaks (Jim Meyering), fix compilation when building
+      without Xen (Guido Guenther), mark translatables strings (Jim Meyering),
+      use virBufferAddLit for constant strings (Jim Meyering), fix
+      make distcheck (Jim Meyering), return values for python bindings (Cole
+      Robinson), trailing blanks fixes (Jim Meyering), gcc-4.3.0 fixes
+      (Mark McLoughlin), use safe read and write routines (Jim Meyering),
+      refactoring of code dealing with hypervisor capabilities (Daniel
+      Berrange), qemudReportError to use virErrorMsg (Cole Robinson),
+      intemediate library and Makefiles for compiling static and coverage
+      rule support (Jim Meyering), cleanup of various leaks (Jim Meyering)</li>
+</ul><h3>0.4.0: Dec 18 2007</h3><ul><li>New features: Compilation on Windows cygwin/mingw (Richard Jones),
       Ruby bindings (David Lutterkort), SASL based authentication for
       libvirt remote support (Daniel Berrange), PolicyKit authentication
       (Daniel Berrange)</li>
-  <li>Documentation: example files for QEMU and libvirtd configurations
+  <li>Documentation: example files for QEMU and libvirtd configuations
       (Daniel Berrange), english cleanups (Jim Paris), CIM and OpenVZ
       references, document &lt;shareable/&gt;, daemon startup when using
       QEMU/KVM, document HV support for new NUMA calls (Richard Jones),

docs/python.html

@@ -2,7 +2,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" /><link rel="stylesheet" type="text/css" href="libvirt.css" /><link rel="SHORTCUT ICON" href="/32favicon.png" /><title>Bindings for other languages</title></head><body><div id="container"><div id="intro"><div id="adjustments"></div><div id="pageHeader"></div><div id="content2"><h1 class="style1">Bindings for other languages</h1><p>Libvirt comes with bindings to support other languages than
 pure C. First the headers embeds the necessary declarations to
-allow direct access from C++ code, but also we have bindings for
+allow direct acces from C++ code, but also we have bindings for
 higher level kind of languages:</p><ul><li>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

docs/storage.html

@@ -84,7 +84,7 @@ full capacity for storage volumes. This value is in bytes. This
 is not applicable when creating a pool.</dd>
 
 <dt>available</dt>
-<dd>Providing the free space available for allocating new volumes
+<dd>Providing the free space available for allocating new volums
 in the pool. Due to underlying device constraints it may not be
 possible to allocate the entire free space to a single volume.
 This value is in bytes. This is not applicable when creating a
@@ -131,8 +131,8 @@ pool it will be the name of the directory in which volumes will
 be created. For device based pools it will tbe directory in which
 devices nodes exist. For the latter <code>/dev/</code> may seem
 like the logical choice, however, devices nodes there are not
-guaranteed stable across reboots, since they are allocated on
-demand. It is preferable to use a stable location such as one
+guarenteed stable across reboots, since they are allocated on
+demand. It is preferrable to use a stable location such as one
 of the <code>/dev/disk/by-{path,id,uuid,label</code> locations.
 </dd>
 <dt>permissions<dt>
@@ -152,7 +152,7 @@ contains the MAC (eg SELinux) label string.
 If a storage pool exposes information about its underlying
 placement / allocation scheme, the <code>device</code> element
 within the <code>source</code> element may contain information
-about its available extents. Some pools have a constraint that
+about its avilable extents. Some pools have a constraint that
 a volume must be allocated entirely within a single constraint
 (eg disk partition pools). Thus the extent information allows an
 application to determine the maximum possible size for a new
@@ -215,8 +215,8 @@ pool it will be the name of the directory in which volumes will
 be created. For device based pools it will tbe directory in which
 devices nodes exist. For the latter <code>/dev/</code> may seem
 like the logical choice, however, devices nodes there are not
-guaranteed stable across reboots, since they are allocated on
-demand. It is preferable to use a stable location such as one
+guarenteed stable across reboots, since they are allocated on
+demand. It is preferrable to use a stable location such as one
 of the <code>/dev/disk/by-{path,id,uuid,label</code> locations.
 </dd>
 <dt>format</dt>
@@ -293,10 +293,10 @@ One of the following options:
 </ul><p>
 When listing existing volumes all these formats are supported
 natively. When creating new volumes, only a subset may be
-available. The <code>raw</code> type is guaranteed always
+available. The <code>raw</code> type is guarenteed always
 available. The <code>qcow2</code> type can be created if
 either <code>qemu-img</code> or <code>qcow-create</code> tools
-are present. The others are dependent on support of the
+are present. The others are dependant on support of the
 <code>qemu-img</code> tool.
 
 </p><h4><a name="StorageBackendFS" id="StorageBackendFS">Filesystem pool</a></h4>
@@ -328,7 +328,7 @@ required.
 <h5>Valid pool format types</h5>
 
 <p>
-The filesystem pool supports the following formats:
+The fileystem pool supports the following formats:
 </p>
 
 <ul><li><code>auto</code> - automatically determine format</li>
@@ -378,7 +378,7 @@ point. It will default to using NFS as the protocol.
 <h5>Valid pool format types</h5>
 
 <p>
-The network filesystem pool supports the following formats:
+The network fileystem pool supports the following formats:
 </p>
 
 <ul><li><code>auto</code> - automatically determine format</li>

include/libvirt/libvirt.h

@@ -372,7 +372,7 @@ extern virConnectAuthPtr virConnectAuthPtrDefault;
  * version * 1,000,000 + minor * 1000 + micro
  */
 
-#define LIBVIR_VERSION_NUMBER 4000
+#define LIBVIR_VERSION_NUMBER 4001
 
 int			virGetVersion		(unsigned long *libVer,
 						 const char *type,

libvirt.spec.in

@@ -17,7 +17,7 @@
 Summary: Library providing a simple API virtualization
 Name: libvirt
 Version: @VERSION@
-Release: 1%{?dist}%{?extra_release}
+Release: 1%{?extra_release}
 License: LGPL
 Group: Development/Libraries
 Source: libvirt-%{version}.tar.gz
@@ -240,6 +240,13 @@ fi
 %doc docs/examples/python
 
 %changelog
+* Mon Mar  3 2008 Daniel Veillard <veillard@redhat.com> - 0.4.1-1
+- Release of 0.4.1
+- Storage APIs
+- xenner support
+- lots of assorted improvements, bugfixes and cleanups
+- documentation and localization improvements
+
 * Tue Dec 18 2007 Daniel Veillard <veillard@redhat.com> - 0.4.0-1
 - Release of 0.4.0
 - SASL based authentication