Thomas, am Sun, Dec 12, 2010 at 11:48:56AM +0100 hast du folgendes geschrieben: > I also agree that this needs to be resolved before the release and in my > opinion this bugs severity should be at least important, if not critical > because it will "break" Xen dom0 functionality of existing systems when > they are upgraded from Lenny to Squeeze. > > Of course this could be "fixed" by the user of the package by selecting > an appropriate GRUB_DEFAULT value, but this is likely to break if new > kernel versions are installed. > > The appropriate fix is very simple, just rename /etc/grub.d/20_linux_xen > to /etc/grub.d/09_linux_xen or some other number in the range of 06-09. > > A workaround which will work, even if new kernel versions or grub > upgrades are installed, the user can create a > symlink /etc/grub.d/09_linux_xen wich points > to /etc/grub.d/20_linux_xen. (This of course will result in duplicate > grub menuentries for Xen, but should not hurt otherwise.)
are grub1 installations (which were the default for Lenny AFAIK) auto-upgraded to grub2 during the dist-upgrade? If not, it shouldn't break existing Xen dom0s? Kind regards Philipp Kern
signature.asc
Description: Digital signature