"Normal" kernel being before the Xen hypervisor in Squeeze

[Thomas Goirand]

On 12/12/2010 01:03 AM, Julien Cristau wrote:
> On Sat, Dec 11, 2010 at 16:51:03 +0000, Jonathan Wiltshire wrote:
> 
>> On Fri, Dec 10, 2010 at 05:40:02PM +0100, Julien Cristau wrote:
>>> On Sat, Dec 11, 2010 at 00:19:34 +0800, Thomas Goirand wrote:
>>>
>>>> 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.
>>>>
>>> No.
>>
>> I'm not sure what to make of this; do you mean you think "no" to the
>> Xen question, or to filing an RC report about it?
>>
> I'm saying this is not RC in my opinion, it's wishlist.  The rest is up
> to the grub maintainers.
> 
> Cheers,
> Julien

For me, it's a grave regression that can put a production environment
into big troubles, and it would deserved a RC for me, but because:
- of Julien's opinion
- that the RT should have the final word
- that I respect this view
- that delaying Squeeze just for this might not be a good idea
- not everyone really cares much about Xen in Debian

... then I sent my report as a wishlist as requested.

However, it would be very appreciated if the Grub maintainers could
consider solving the issue before the release. :)

I would also like to hear what type of modification are involved to make
it a clean way. *Please* let us know asap what's the best solution to
fix. I'd be happy to help if needed.

Another thing I failed to mention and that I wanted to write about. Grub
in fact doesn't only sets the hypervisor at the end of the list, but
choices in the boot menu are totally inverted. Let me explain. To me, it
should be:

- Debian Linux 2.6.32-5-xen with Xen hypervisor
- Debian Linux 2.6.32-5
- Debian Linux 2.6.32-5-xen

But currently, it does:

- Debian Linux 2.6.32-5-xen
- Debian Linux 2.6.32-5
- Debian Linux 2.6.32-5-xen with Xen hypervisor

In other words, when installing Xen, grub will make the kernel with dom0
patch be the default, but without the hypervisor running. This looks a
bit weird, no? :)

Thomas