From: Daniel Veillard
Date: Tue, 11 Jul 2006 16:57:03 +0000 (+0000)
Subject: * configure.in libvirt.spec.in docs/* NEWS: preparing release of
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=0798941a85e36cadf569e91b1bc34a07c36d582e;p=libvirt.git
* configure.in libvirt.spec.in docs/* NEWS: preparing release of
libvirt-0.1.3
* src/xend_internal.c: uninitialized var and disable TCP slow start
Daniel
---
diff --git a/ChangeLog b/ChangeLog
index a9b6cbb2a1..6aea8e9078 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+Tue Jul 11 18:03:51 CEST 2006 Daniel Veillard
+
+ * configure.in libvirt.spec.in docs/* NEWS: preparing release of
+ libvirt-0.1.3
+ * src/xend_internal.c: uninitialized var and disable TCP slow start
+
Mon Jul 10 14:19:52 CEST 2006 Daniel Veillard
* docs/format.html docs/libvir.html docs/news.html: updated the XML
@@ -14,7 +20,6 @@ Fri Jul 7 09:47:14 EDT 2006 Daniel Berrange
an sexpr GET on /xend/domain/[ID] instead of listing all names
and iterating over /xend/domain/[NAME]. Reduces the running time
and number of GETs from O(n^2) to O(n).
- * src/xend_internal.c: fixed xenDaemonOpen() to try both unix and
Wed Jul 5 17:11:32 IST 2006 Mark McLoughlin
diff --git a/NEWS b/NEWS
index aab22611bb..2674a7b147 100644
--- a/NEWS
+++ b/NEWS
@@ -5,6 +5,16 @@
http://libvirt.org/news.html
Releases
+0.1.3: Jul 11 2006:
+ - bugfixes: build as non-root, fix xend access when root, handling of
+ empty XML elements (Mark McLoughlin), XML serialization and parsing fixes
+ (Mark McLoughlin), allow to create domains without disk (Mark
+ McLoughlin),
+ - improvement: xenDaemonLookupByID from O(n^2) to O(n) (Daniel Berrange),
+ support for fully virtualized guest (Jim Fehlig, DV, Mark McLoughlin)
+ - documentation: augmented to cover hvm domains
+
+
0.1.2: Jul 3 2006:
- headers include paths fixup
- proxy mechanism for unpriviledged read-only access by httpu
diff --git a/configure.in b/configure.in
index ba28df135b..fc5694e723 100644
--- a/configure.in
+++ b/configure.in
@@ -5,7 +5,7 @@ AC_CANONICAL_HOST
LIBVIRT_MAJOR_VERSION=0
LIBVIRT_MINOR_VERSION=1
-LIBVIRT_MICRO_VERSION=2
+LIBVIRT_MICRO_VERSION=3
LIBVIRT_MICRO_VERSION_SUFFIX=
LIBVIRT_VERSION=$LIBVIRT_MAJOR_VERSION.$LIBVIRT_MINOR_VERSION.$LIBVIRT_MICRO_VERSION$LIBVIRT_MICRO_VERSION_SUFFIX
LIBVIRT_VERSION_INFO=`expr $LIBVIRT_MAJOR_VERSION + $LIBVIRT_MINOR_VERSION`:$LIBVIRT_MICRO_VERSION:$LIBVIRT_MINOR_VERSION
diff --git a/docs/format.html b/docs/format.html
index ba5c652920..c211813845 100644
--- a/docs/format.html
+++ b/docs/format.html
@@ -86,7 +86,7 @@ poweroff. There is various actions possible when this happen:
- destroy
</domain>
While the format may be extended in various ways as support for more
hypervisor types and features are added, it is expected that this core subset
will remain functional in spite of the evolution of the library.
Here is an example of a domain description used to start an fully
+(added in 0.1.3):
Here is an example of a domain description used to start a fully
virtualized (a.k.a. HVM) Xen domain. This requires hardware virtualization
support at the processor level but allows to run unmodified operating
systems:
<domain type='xen' id='3'>
@@ -118,8 +118,8 @@ systems:<domain type='xen' id='3'>
</domain>
There is a few things to notice specifically for HVM domains:
- 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 ill extract the boot informations from the boot device specified in
- a separate boot element
+ which will extract the boot informations from the boot device specified
+ in a separate boot element
- the <devices> section includes an emulator entry pointing to an
additional program in charge of emulating the devices
- the disk entry indicates in the dev target section that the emulation
@@ -127,6 +127,7 @@ systems:
<domain type='xen' id='3'>
- the <devices> section also include at least one entry for the
graphic device used to render the os. Currently there is just 2 types
possible 'vnc' or 'sdl'
-
It is likely that the HVM description gets additional elements and
-attributes as the support for fully virtualized domain expands especially for
-the kind of devices emulated and the graphic options offered.