Release notes addition for Xen support in Debian

[Martin Zobel-Helas]

Hi, 

On Tue Dec 28, 2010 at 15:34:21 +0800, Thomas Goirand wrote:
> Hi,
> 
> I intend to have the attached document added to the Squeeze release
> notes. Also, what's the way to have it included? Should I send it as a
> wishlist bug to the "release-notes" package, or something like that?

In general I support this. Those are changes worth mentioning. On the
other hand your text reads more like a howto, which IMHO should be
content for wiki.debian.org. Maybe have the release notes linking a wiki
document instead?

> Could others please give me comments on this? Also, some correction for
> my (poor) English would be welcome when/if you spot issues.

You are aware that we have debian-l10n-english at l.d.o for exactly that
reason?

Also i spotted that some of your wording is quite negative
("Unfortunaly", "As a consequence", "Another thing that you have to take
care about", ...). I would like to suggest we come up with at least a
neutral wording here. As I am not a native english speaker either, I
took the liberty to Cc debian-l10n-english at l.d.o for a help of rewording
the whole text.

Cheers,
Martin


| 4.7.4. Upgrading with Xen installed, and Kernel enumeration order issue with
| Xen
| 
| In Lenny, using grub legacy, the following kernel order was respected: - Xen
| hypervisor with Xen dom0 kernel - Normal (eg: without dom0 support) kernel -
| Xen dom0 kernel (without they hypervisor)
| 
| This order was the natural expected one, because if you installed Xen, it will
| simply boot the hypervisor and it's dom0 by default as expected.
| 
| Unfortunately, in Squeeze, when running with Grub2, this isn't what is
| happening. By default, the order is the exact opposite: - Xen dom0 kernel
| (without they hypervisor) - Normal (eg: without dom0 support) kernel - Xen
| hypervisor with Xen dom0 kernel
| 
| As a consequence, if you have Xen installed and expect to boot with it by
| default, you have to tweak grub2 configuration. One of the way to hack before
| the grub maintainers can fix it the proper way could be to simply do:
| 
| ln -s 20_linux_xen /etc/grub.d/09_linux_xen_first dpkg-reconfigure grub-pc
| 
| so that Xen is loaded first, by default, when using Grub2.
| 
| Another thing that you have to take care about when upgrading from Lenny, is
| that currently, Xen isn't upgraded to the 4.0 version that you should be
| expecting in Squeeze. So, after you finished the dist-upgrade, it is advised to
| check that Xen 4.0 and the corresponding dom0 kernel are installed. Under the
| 64 bits architecture, the following command will fix this:
| 
| apt-get install xen-utils-common xen-utils-4.0 xenstore-utils libxenstore3.0
| xen-hypervisor-4.0-amd64 linux-image-2.6.32-5-xen-amd64
| 
| Here is the corresponding for 32 bits:
| 
| apt-get install xen-utils-common xen-utils-4.0 xenstore-utils libxenstore3.0
| xen-hypervisor-4.0-i686 linux-image-2.6.32-5-xen-i686
| 
| Also, if you require HVM support, you will need to install the Xen Qemu device
| model, which is now a separate package:
| 
| apt-get install xen-qemu-dm-4.0
| 
| It is also important to notice that your domU wont be able to use sda1 (for
| example) as device name for their HDD. This naming scheme has been removed from
| Xen because of a request from the mainline kernel maintainers. Instead, you
| should use xvda1 (as a corresponding example) instead.
| 
| 


-- 
 Martin Zobel-Helas <zobel at debian.org>  | Debian System Administrator
 Debian & GNU/Linux Developer           |           Debian Listmaster
 Public key http://zobel.ftbfs.de/5d64f870.asc   -   KeyID: 5D64 F870
 GPG Fingerprint:  5DB3 1301 375A A50F 07E7  302F 493E FB8E 5D64 F870