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

[Justin B Rye <jbr@edlug.org.uk>]

Julien Cristau wrote:
> 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.

The most recent version I saw was:

# <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: 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>
# 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.
# </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 is not available in the Xen
# pvops support available in the upstream Linux kernel. 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>

This has a couple of minor English glitches; the only place this
really matters is that it can be hard to follow what kernels it's
talking about.  When it says "if you run a pvops kernel [...] like
the Xen kernel 2.6.32 of Squeeze", this seems a confusing way of
putting it - given that our target audience is running Lenny, they
may conclude the paragraph doesn't apply to them and can be skipped.

On the other hand "Lenny 2.6.26 forward ported Xen patch" is talking
about kernels using the old "Xenlinux" patch forward-ported from
2.6.18, right?

I attach an attempted debian-l10n-english rewrite.

(paravirt-ops or pv_ops or pvops?  I'll be lazy.)

By the way, don't forget to update http://wiki.debian.org/Xen to
recognise Squeeze as Stable...
-- 
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 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>
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>