[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#608253: marked as done ([release-notes] Xen upgrading)

Your message dated Tue, 1 Feb 2011 23:04:42 +0100
with message-id <[🔎] 20110201220442.GK10244@radis.liafa.jussieu.fr>
and subject line Re: Bug#608253: [Pkg-xen-devel] Release notes addition for Xen support	in Debian
has caused the Debian Bug report #608253,
regarding [release-notes] Xen upgrading
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

608253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=608253
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: normal
Tags: patch


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,

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 @@
+<section id="xen-upgrades">
+<title>Xen upgrades</title>
+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:
+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.
+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.
 <programlisting condition="fixme">

--- End Message ---
--- Begin Message ---
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


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

    issues: add xen section
    Signed-off-by: Julien Cristau <jcristau@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>.
+<section id="xen-upgrades" arch="amd64;i386">
+<title>Xen upgrades</title>
+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
+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.
+&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.
 <section id="pam_userdb">
 <title>pam_userdb.so breakage with newer libdb</title>

Attachment: signature.asc
Description: Digital signature

--- End Message ---

Reply to: