All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Behaviour of update-grub when Xen enabled kernels are installed.
Date: Wed, 28 May 2008 15:39:30 +0200	[thread overview]
Message-ID: <20080528133930.GB26495@thorin> (raw)
In-Reply-To: <1210498598.14928.36.camel@localhost.localdomain>


No reply...  if you're still interested in this, I suggest you contact
the people who set the current behaviour and involve them in the discussion,
to see if they have any objections to what you propose.

On Sun, May 11, 2008 at 10:36:38AM +0100, Ian Campbell wrote:
> Hi all,
> 
> The version of update-grub in Debian's grub-legacy packages[0] has an
> interesting feature where it attempts to detect when I kernel is
> compiled for Xen and chooses to include it in the menu depending on
> whether it is running inside a Xen guest domain or not[1].
> 
> As described at [2] this behaviour has been broken by the latest kernels
> which due to the paravirt_ops (CONFIG_PARAVIRT) framework which means
> that these kernels are now bootable both native and as a Xen guest
> domain.
> 
> Robert asked me to bring the issue here and to ask the question of
> whether or not this behaviour would be welcomed as a patch to grub 2.
> 
> Personally I am not a fan of this behaviour since it causes the wrong
> thing to occur in several circumstances, i.e. installing into a chroot
> or switching back and forth between fully- and para-virtualised
> operation and as time moves on CONFIG_PARAVIRT will become the norm and
> the behaviour less necessary in general. What is the opinion of the grub
> 2 devs?
> 
> Cheers,
> Ian.
> [0] For those not familiar with Xen the classical Xen kernels cannot be
> run on bare metal so there is an argument that it makes little sense to
> include them in the menu for the control domain, conversely including a
> native kernel in the menu for a guest domain is not terribly useful
> either. CONFIG_PARAVIRT (2.6.22+) changes this and such kernel is now
> bootable on native and under Xen.
> [1]
> http://svn.debian.org/viewsvn/pkg-grub/grub/trunk/debian/update-grub?view=auto
> [2]
> http://lists.alioth.debian.org/pipermail/pkg-grub-devel/2008-April/004701.html http://lists.alioth.debian.org/pipermail/pkg-grub-devel/2008-May/004821.html
> 
> 
> -- 
> Ian Campbell
> 
> Waste not fresh tears over old griefs.
> 		-- Euripides



> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel


-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)



  reply	other threads:[~2008-05-28 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11  9:36 Behaviour of update-grub when Xen enabled kernels are installed Ian Campbell
2008-05-28 13:39 ` Robert Millan [this message]
2008-05-30  7:45   ` Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080528133930.GB26495@thorin \
    --to=rmh@aybabtu.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.