From: "Marcel J.E. Mol" <marcel@mesa.nl>
To: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] pygrub/GrubConf: fix boot problem for fedora 19 grub.cfg (2nd attempt)
Date: Wed, 26 Jun 2013 20:14:53 +0200 [thread overview]
Message-ID: <20130626181453.GA9168@joshua.mesa.nl> (raw)
In-Reply-To: <1372254646.7337.85.camel@zakaz.uk.xensource.com>
On Wed, Jun 26, 2013 at 02:50:46PM +0100, Ian Campbell wrote:
> On Mon, 2013-06-24 at 18:21 +0200, Marcel J.E. Mol wrote:
> > Booting a fedora 19 domU failed because a it could not properly
> > parse the grub.cfg file. This was cased by
> >
> > set default="${next_entry}"
> >
>
> Any chance you could send us an example of the actual problematic
> configuration file, ideally as a patch adding a new file to
> tools/pygrub/examples/. That "test suite" is rather rudimentary (to the
> extent I'm a bit embarrassed to call it a suite...) but collecting them
> when a bug is fixed is a good way to grow it.
The grub.cfg is autogenerated in Fedora 19. I'll add a patch with the grub.cfg
that failed on me.
--
======-------- Marcel J.E. Mol MESA Consulting B.V.
=======--------- ph. +31-(0)6-54724868 P.O. Box 112
=======--------- marcel@mesa.nl 2630 AC Nootdorp
__==== www.mesa.nl ---____U_n_i_x______I_n_t_e_r_n_e_t____ The Netherlands ____
They couldn't think of a number, Linux user 1148 -- counter.li.org
so they gave me a name! -- Rupert Hine -- www.ruperthine.com
next prev parent reply other threads:[~2013-06-26 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 16:21 [PATCH] pygrub/GrubConf: fix boot problem for fedora 19 grub.cfg (2nd attempt) Marcel J.E. Mol
2013-06-26 13:50 ` Ian Campbell
2013-06-26 18:14 ` Marcel J.E. Mol [this message]
2013-06-26 13:52 ` George Dunlap
2013-06-26 13:57 ` Wei Liu
2013-06-26 18:17 ` Marcel J.E. Mol
2013-06-26 15:01 ` Konrad Rzeszutek Wilk
2013-06-26 16:05 ` George Dunlap
2013-06-27 11:31 ` Ian Campbell
2014-04-04 15:15 ` Ian Jackson
2013-07-02 15:01 ` Konrad Rzeszutek Wilk
2013-07-02 23:07 ` Marcel J.E. Mol
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=20130626181453.GA9168@joshua.mesa.nl \
--to=marcel@mesa.nl \
--cc=Ian.Campbell@citrix.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).