From: "Sven Köhler" <sven.koehler@gmail.com>
To: Juergen Gross <jgross@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-users] pvgrub: Error 9: Unknown boot failure
Date: Tue, 27 Sep 2016 14:09:59 +0200 [thread overview]
Message-ID: <806f8ab3-beef-3646-8d6b-cc1d9572e57f@gmail.com> (raw)
In-Reply-To: <1d434e72-2f4e-c541-efdf-30a254c91179@suse.com>
Am 27.09.2016 um 14:02 schrieb Juergen Gross:
> On 27/09/16 13:13, Sven Köhler wrote:
>> Am 27.09.2016 um 07:31 schrieb Juergen Gross:
>>> On 27/09/16 00:48, Sven Köhler wrote:
>>>> Am 26.09.2016 um 07:43 schrieb Juergen Gross:
>>>>> On 25/09/16 18:04, Sven Köhler wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I'm experiencing the bug below which was discussed on xen-devel December
>>>>>> last year buy Ian and Juergen. I'm using xen-pvgrub-4.7.0 on Gentoo.
>>>>>>
>>>>>> The bug only seems to occur with the last domU booted on my machine.
>>>>>> Where do I find a patch that fixes that?
>>>>>
>>>>> The issue back in December was fixed by commit
>>>>> c8eb0ec277ae387e78d685523e0fee633e46f046 which is included in Xen 4.7.
>>>>> Either gentoo didn't update to the official Xen 4.7 release (including
>>>>> pvgrub) or you are seeing a new issue.
>>>>
>>>> From the looks of it, the Gentoo package is using the grub from the
>>>> xen-4.7.0 tarball.
>>>>
>>>> I downgraded to pvgrub 4.6.3 and the problem went away.
>>>>
>>>> So I assume I'm seeing a new issue. How do I debug it?
>>>
>>> Interesting. Just tested it on upstream Xen and saw the same problem
>>> with a rather old guest kernel (3.0 based, xen flavor), while a newer
>>> kernel (4.1, pvops) is working.
>>>
>>> Can you give me some more details about the kernel you are trying to
>>> boot?
>>
>> It's an unmodified 4.4.21 kernel which I compile by hand. The config is
>> attached. Does that help?
>
> Not really. OTOH I think I don't need more help, as I've found a problem
> in pvgrub. I have a patch which seems to correct the issue. Are you fine
> with me adding you as the original reporter of the problem in the patch?
Yes, I'm fine with adding me as the reporter.
Do you want me to test the patch first?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-09-27 12:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ns8sjf$etc$1@blaine.gmane.org>
[not found] ` <53d7467a-5c5a-8f48-fae5-1b21b8e7459e@suse.com>
[not found] ` <9fc0a827-b452-50bb-6923-3a650b104b56@gmail.com>
2016-09-27 5:31 ` [Xen-users] pvgrub: Error 9: Unknown boot failure Juergen Gross
2016-09-27 11:13 ` Sven Köhler
2016-09-27 12:02 ` Juergen Gross
2016-09-27 12:09 ` Sven Köhler [this message]
2016-09-27 12:52 ` Juergen Gross
2016-09-27 23:33 ` Sven Köhler
2016-09-28 3:50 ` Juergen Gross
2016-12-07 16:10 ` Sven Köhler
2016-12-07 16:18 ` Juergen Gross
2016-12-07 16:28 ` Jan Beulich
2016-12-07 16:38 ` Samuel Thibault
2016-12-07 16:54 ` Sven Köhler
[not found] ` <584846D402000078001266C3@suse.com>
2016-12-07 19:34 ` Juergen Gross
2016-12-07 16:33 ` Jan Beulich
2016-12-07 16:39 ` Sven Köhler
[not found] ` <5848480702000078001266D5@suse.com>
2016-12-07 19:34 ` Juergen Gross
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=806f8ab3-beef-3646-8d6b-cc1d9572e57f@gmail.com \
--to=sven.koehler@gmail.com \
--cc=jgross@suse.com \
--cc=xen-devel@lists.xenproject.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 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).