On Thu, Dec 30, 2010 at 12:40:32AM +0800, Thomas Goirand wrote: > > Thanks. Indeed, there was some possible confusion. Patched accordingly. > > Please find the new patch attached to this email. >
See below for one more comment.. > 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 @@ > </para> > </section> > > +<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 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. > +</para> > +</section> Actually the sd* naming hasn't been removed from *Xen* itself, just from the pvops (upstream kernel.org) Linux kernel xen-blkfront driver! -- Pasi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
