Bug#608253: [Pkg-xen-devel] Release notes addition for Xen support in Debian
- To: debian-l10n-english@lists.debian.org
- Cc: Julien Cristau <jcristau@debian.org>, Ian Campbell <ijc@hellion.org.uk>, Thomas Goirand <thomas@goirand.fr>, 608253@bugs.debian.org, Pasi Kärkkäinen <pasik@iki.fi>, Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>, debian-doc@lists.debian.org, debian-kernel@lists.debian.org
- Subject: Bug#608253: [Pkg-xen-devel] Release notes addition for Xen support in Debian
- From: Justin B Rye <jbr@edlug.org.uk>
- Date: Sun, 30 Jan 2011 19:43:23 +0000
- Message-id: <[🔎] 20110130194323.GA10472@xibalba.demon.co.uk>
- Mail-followup-to: debian-l10n-english@lists.debian.org, Julien Cristau <jcristau@debian.org>, Ian Campbell <ijc@hellion.org.uk>, Thomas Goirand <thomas@goirand.fr>, 608253@bugs.debian.org, Pasi Kärkkäinen <pasik@iki.fi>, Debian Xen Team <pkg-xen-devel@lists.alioth.debian.org>, debian-doc@lists.debian.org, debian-kernel@lists.debian.org
- Reply-to: Justin B Rye <jbr@edlug.org.uk>, 608253@bugs.debian.org
- In-reply-to: <[🔎] 4D45B36B.1060400@goirand.fr>
- References: <20101231104719.GX2754@reaktio.net> <1293797103.5576.6.camel@Nokia-N900-42-11> <[🔎] 1294148311.3831.197.camel@zakaz.uk.xensource.com> <[🔎] 20110125100129.GY30701@radis.liafa.jussieu.fr> <[🔎] 20110125153423.GA25353@xibalba.demon.co.uk> <[🔎] 20110129154107.GP10244@radis.liafa.jussieu.fr> <[🔎] 1296320962.5101.2.camel@Nokia-N900-42-11> <[🔎] 1296322371.20804.137.camel@localhost.localdomain> <[🔎] 20110129231339.GS10244@radis.liafa.jussieu.fr> <[🔎] 4D45B36B.1060400@goirand.fr>
Thomas Goirand wrote:
> I don't want to point fingers here (so I wont check who's involved), but
> I've been advised to point at the wiki. Anyway, this paragraph can now
> be removed if the issue has been fixed.
I haven't seen any claim of a fix for the issue that xen users need to
upgrade manually; just a change in the approved manual procedure.
We had:
# Upgrades from Lenny will not automatically install Xen version 4.0. 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.
Apparently now that there are xen-linux-system-2.6-xen-* metapackages
in Squeeze this should read something like:
Upgrades from Lenny will not automatically install Xen version 4.0.
Instead you should manually install a xen-linux-system-2.6-xen-686 or
xen-linux-system-2.6-xen-amd64 metapackage, which will handle the
dependencies and should facilitate future upgrades. See the wiki page
for configuration instructions.
My apologies if this is a clueless question, but I'll ask again: how
does this interact with the requirement in the generic upgrade
procedure for a kernel change to handle udev? Should we be advising
people to do this xen kernel switch early or late in the upgrade?
I attach an updated d-l-eified version (this paragraph was the one
that didn't need any proofreading).
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
<section id="xen-upgrades">
<title>Xen upgrades</title>
<para>
If you installed Xen on Lenny, 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 Squeeze: the non-Xen kernel
will boot per 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 Lenny will not automatically install Xen version 4.0.
Instead you should manually install a xen-linux-system-2.6-xen-686 or
xen-linux-system-2.6-xen-amd64 metapackage, which will handle the
dependencies and should facilitate future upgrades. See the wiki page
for configuration instructions.
</para>
<para>
Squeeze's 2.6.32 Xen kernel uses pvops instead of the forward-ported
Xenlinux patch. This means that on Squeeze your domU won't be able
to use (for example) sda1 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) xvda1, which is compatible with
both old and new Xen kernels.
</para>
</section>
Reply to: