Re: [Pkg-xen-devel] Release notes addition for Xen support in Debian
On 12/29/2010 07:40 PM, Justin B Rye wrote:
> Martin Zobel-Helas wrote:
>> Thomas, if you don't mind, i still would like to tweak the text a bit.
> Most of your changes look to me like definite improvements, except:
>>> This does not happen under GRUB 2 in Squeeze. Instead, the non-Xen
>>> kernel will boot by default.
>> This behavior changed with GRUB 2 in Squeeze and the non-Xen kernel will
>> boot per default.
> An improvement, but the "and" is a bit weak - maybe...
> This behavior has changed with GRUB 2 in Squeeze: the non-Xen kernel
> will boot by default.
>>> Also, upgrading from the Lenny version of Xen does not automatically install
>>> the current 4.0 version.
>> When upgrading from Lenny version 4.0 of the Xen package will not
>> install automatically.
> No, this needs clearer punctuation ("Lenny version 4.0"?),
> preferably without the dangling modifier (version 4.0 of Xen isn't
> "upgrading"). If you don't like my original version, how about:
> Upgrades from Lenny will not automatically install Xen version 4.0.
Thanks. Indeed, there was some possible confusion. Patched accordingly.
Please find the new patch attached to this email.
Thomas Goirand (zigo)
--- release-notes/en/upgrading.dbk.orig 2010-12-29 17:15:03.000000000 +0800
+++ release-notes/en/upgrading.dbk 2010-12-30 00:37:17.000000000 +0800
@@ -1349,6 +1349,32 @@
+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:
+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.
+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.