"Normal" kernel being before the Xen hypervisor in Squeeze

[Thomas Goirand]

Hi there,

I did some Lenny to Squeeze upgrades lately, on some test servers
running Xen. And I've noticed that, in Lenny, the Xen hypervisor is set
to be the first and default choice of Grub. But in Squeeze, this
behavior changes, and the hypervisor isn't the default anymore.

The result in a production server running some VM would be that no
virtual machine would be started (because Xen not running) just right
after the upgrade, and without any human intervention. This can be quite
bad, especially if, like many, you don't really know Grub 2.

So, my question is: was this intentional, and could it be reverted? I
really think that if you install Xen, it's to be able to run it by
default. Or at least, a big big big warning should come, saying that it
wont be the default (maybe a debconf critical warning ?).

I was tempted to write a RC bug report here. Please let me know what you
think of this, and I may write one report.

Regards,

Thomas Goirand