Bug#608253: [release-notes] Xen upgrading
Package: release-notes
Severity: normal
Tags: patch
Hi,
I've worked-out a patch for the English release-notes. It consist of few
advice on what to do to have a smooth upgrade to Squeeze when running Xen.
This has been reviewed for both content and English correctness (thanks
to Martin's great help here).
Please consider including this text in the Squeeze release-notes,
Cheers,
Thomas Goirand (zigo)
--- System information. ---
Architecture: amd64
Kernel: Linux 2.6.32-5-amd64
Debian Release: squeeze/sid
500 testing mirrors.sohu.com
--- release-notes/en/upgrading.dbk.orig 2010-12-29 17:15:03.000000000 +0800
+++ release-notes/en/upgrading.dbk 2010-12-29 17:32:42.000000000 +0800
@@ -1349,6 +1349,32 @@
</para>
</section>
+<section id="xen-upgrades">
+<title>Xen upgrades</title>
+<para>
+If you installed Xen on Lenny, the kernel booted by grub-legacy per
+default was the one providing a Xen hypervisor and dom0 support. This
+behavior changed with GRUB 2 in Squeeze and the non-Xen kernel will
+boot per default. If you need Xen and expect to boot with it by default,
+find further configuration hints at:
+http://wiki.debian.org/Xen#Installationandconfiguration
+</para>
+<para>
+When upgrading from Lenny, version 4.0 of the Xen package will not
+install automatically. Instead you need to install Xen 4.0 and a
+corresponding dom0 kernel explicitly. See the wiki page for instructions on
+how to set up the Xen hypervisor and dom0 kernel under Squeeze.
+</para>
+<para>
+Be aware that, if you run a pvops kernel for your domU, like the Xen kernel
+2.6.32 of Squeeze, your domU won't be able to use (for example) sda1 as a
+device name for its hard drive. This naming scheme has been removed from Xen
+upon request of the mainline kernel maintainers. Instead you should use (as
+a corresponding example) xvda1, which will always work, including when running
+Lenny 2.6.26 forward ported Xen patch.
+</para>
+</section>
+
</section>
<programlisting condition="fixme">
Reply to: