[Pkg-xen-devel] Bug#608253: Release notes addition for Xen support in Debian

[Julien Cristau]

On Tue, Jan 25, 2011 at 11:01:29 +0100, Julien Cristau wrote:

> Hi,
> 
> could somebody please come up with a patch for the release notes re:
> xen?  It seems there were more incremental changes after the last patch
> posted on this bug.
> 
Committed the following, please open new bugs if something else is
needed.

Cheers,
Julien

commit 30275353049b1a0b21032f81eb861ef013b6e753
Author: Julien Cristau <jcristau at debian.org>
Date:   Tue Feb 1 23:02:48 2011 +0100

    issues: add xen section
    
    Bug#608253
    
    Signed-off-by: Julien Cristau <jcristau at debian.org>

diff --git a/en/issues.dbk b/en/issues.dbk
index 5daa81f..14b80e0 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -84,6 +84,34 @@ or <ulink url="http://grml.org">grml</ulink>.
 </para>
 </section>
 
+<section id="xen-upgrades" arch="amd64;i386">
+<title>Xen upgrades</title>
+<para>
+If you installed Xen on &oldreleasename;, the default kernel booted by
+GRUB Legacy was the one providing a Xen hypervisor and dom0 support.
+This behavior has changed with GRUB 2 in &releasename;: the non-Xen kernel
+will boot by default. If you need Xen and expect to boot with it by default,
+there are configuration hints at
+http://wiki.debian.org/Xen#Installationandconfiguration
+</para>
+<para>
+Upgrades from &oldreleasename; will not automatically install Xen version 4.0.
+You should install the <systemitem
+role="package">xen-linux-system-2.6-xen-amd64</systemitem> or <systemitem
+role="package">xen-linux-system-2.6-xen-686</systemitem> package to ensure the
+Xen hypervisor and suitable dom0 kernel are installed, and to make future
+upgrades easier.
+</para>
+<para>
+&Releasename;'s 2.6.32 Xen kernel uses pvops instead of the forward-ported
+Xenlinux patch. This means that on &releasename; your domU won't be able
+to use (for example) <filename>sda1</filename> as a device name for its hard
+drive, since this naming scheme is not available under pvops. Instead you
+should use (as a corresponding example) <filename>xvda1</filename>, which is
+compatible with both old and new Xen kernels.
+</para>
+</section>
+
 <section id="pam_userdb">
 <title>pam_userdb.so breakage with newer libdb</title>
 <para>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20110201/0d96b221/attachment.pgp>