From: "Marcel J.E. Mol" <marcel@mesa.nl>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] pygrub/GrubConf: fix boot problem for fedora 19 grub.cfg (2nd attempt)
Date: Wed, 3 Jul 2013 01:07:09 +0200 [thread overview]
Message-ID: <20130702230708.GA16609@joshua.mesa.nl> (raw)
In-Reply-To: <20130702150118.GA5830@phenom.dumpdata.com>
On Tue, Jul 02, 2013 at 11:01:18AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Jun 24, 2013 at 06:21:32PM +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}"
> >
> > This statement actually is within an 'if' statement, so maybe it would
> > be better to skip code within if/fi blocks...
> > But this patch seems to work fine.
> >
> > Signed-off-by: Marcel Mol <marcel@mesa.nl>
>
> Hey Marcel,
>
> Thank you for finding the patch. As you have seen it is both in Xen 4.4 and
> it is part of the Fedora 19 Xen 4.2 candidate patches. I was wondering if you
> have the time to leave feedback at https://admin.fedoraproject.org/updates/FEDORA-2013-11837/xen-4.2.2-10.fc19
> for the updated Xen RPMs which have this patch (and also some other ones)?
Done
>
> And again - thank you for taking the time to dig in PyGrub and to submit the
> patch!
Glad to be of help. My server was still running the rawhide from
fedora core 8, being the latest dom0 fedora for a long time. I just
thought it was about time to update it :) Fedora 19 was almost there
so I just gave it a try on a test machine. Running the old domU cliens
on the new xen server went fine and as I planned to also update the domU
clients, I first tried installing a fresh fedora 19 client. And we know what
happened then...
It was a bit difficult to debug the code as I'm not that fluent in python and
somehow the error message was vague as it does not indicate the real code
location where the problem occured.
Thanks,
-Marcel
--
======-------- 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
prev parent reply other threads:[~2013-07-02 23:07 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
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 [this message]
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=20130702230708.GA16609@joshua.mesa.nl \
--to=marcel@mesa.nl \
--cc=konrad.wilk@oracle.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).