From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Jan Beulich' <JBeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"Julien Grall (julien.grall@arm.com)" <julien.grall@arm.com>,
'BorisOstrovsky' <boris.ostrovsky@oracle.com>,
"xen-devel(xen-devel@lists.xenproject.org)"
<xen-devel@lists.xenproject.org>
Subject: Re: debian stretch dom0 + xen 4.9 fails to boot
Date: Wed, 7 Jun 2017 15:06:34 +0000 [thread overview]
Message-ID: <ee93e45315794a3db4aa21beefb62e52@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <593813E602000078001605F7@prv-mh.provo.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 07 June 2017 13:56
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Julien Grall (julien.grall@arm.com) <julien.grall@arm.com>; Andrew
> Cooper <Andrew.Cooper3@citrix.com>; xen-devel(xen-
> devel@lists.xenproject.org) <xen-devel@lists.xenproject.org>;
> 'BorisOstrovsky' <boris.ostrovsky@oracle.com>; Juergen Gross
> <jgross@suse.com>
> Subject: RE: [Xen-devel] debian stretch dom0 + xen 4.9 fails to boot
>
> >>> On 07.06.17 at 14:46, <Paul.Durrant@citrix.com> wrote:
> >> -----Original Message-----
> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> Sent: 07 June 2017 13:00
> >> To: Paul Durrant <Paul.Durrant@citrix.com>
> >> Cc: Julien Grall (julien.grall@arm.com) <julien.grall@arm.com>; Andrew
> >> Cooper <Andrew.Cooper3@citrix.com>; xen-devel(xen-
> >> devel@lists.xenproject.org) <xen-devel@lists.xenproject.org>;
> >> 'BorisOstrovsky' <boris.ostrovsky@oracle.com>; Juergen Gross
> >> <jgross@suse.com>
> >> Subject: RE: [Xen-devel] debian stretch dom0 + xen 4.9 fails to boot
> >>
> >> >>> On 07.06.17 at 13:55, <Paul.Durrant@citrix.com> wrote:
> >> >> From: Jan Beulich [mailto:JBeulich@suse.com]
> >> >> Sent: 07 June 2017 12:50
> >> >> 2) Provide the E820 map of that box.
> >> >> I'm suspecting the BIOS might use an EBDA without recording it in
> >> >> the low BIOS data area. If it's reported in E820 that would then
> >> >> likely be the final kick for us to obey to the E820 map when
> >> >> determining where to put the trampoline.
> >> >>
> >> >
> >> > The stretch kernel booted bare-metal reports:
> >> >
> >> > [ 0.000000] e820: BIOS-provided physical RAM map:
> >> > [ 0.000000] BIOS-e820: [mem 0x0000000000000000-
> 0x00000000000963ff]
> >> usable
> >> > [ 0.000000] BIOS-e820: [mem 0x0000000000096400-
> 0x000000000009ffff]
> >> reserved
> >>
> >> There we go. Subtracting 4k may then even be too little (depending
> >> what EBDA and low memory values the system reports). Of course
> >> it would be a BIOS bug if they reported some memory they use for
> >> themselves through only E820, as that interface is not required to
> >> be present, and really, really old software wouldn't even know
> >> about it and would hence also be in trouble.
> >>
> >
> > Neither 4k nor 8k seemed to be enough. Even subtracting another
> > 64k doesn't work.
>
> That's rather unexpected.
>
> > I guess I'm going to have to try to write some code to log values to
> > the VGA buffer to see what is going on.
>
> Good luck!
>
That really was too hard... Instead I reverted the patch and stashed EBDA and the initial location of the trampoline and dumped them in __start_xen(). The EBDA tallies with the E820:
(XEN) boot_ebda = 9640
.
.
(XEN) Xen-e820 RAM map:
(XEN) 0000000000000000 - 0000000000096400 (usable)
(XEN) 0000000000096400 - 00000000000a0000 (reserved)
And the initial location of the trampoline appears to be ok...
(XEN) orig_trampoline_phys = 86000
So, still no clue as to why moving the wakeup code around is messing things up.
Paul
> Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-07 15:14 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 14:32 debian stretch dom0 + xen 4.9 fails to boot Paul Durrant
2017-06-06 15:11 ` Jan Beulich
2017-06-06 15:51 ` Paul Durrant
2017-06-06 16:28 ` Paul Durrant
2017-06-06 17:00 ` Boris Ostrovsky
2017-06-07 8:07 ` Jan Beulich
2017-06-07 8:09 ` Paul Durrant
2017-06-07 8:19 ` Paul Durrant
2017-06-07 14:05 ` Boris Ostrovsky
2017-06-07 8:07 ` Paul Durrant
2017-06-07 8:27 ` Jan Beulich
[not found] ` <5937D4FF02000078001602F6@suse.com>
2017-06-07 9:03 ` Juergen Gross
2017-06-07 9:05 ` Paul Durrant
2017-06-07 9:09 ` Andrew Cooper
2017-06-07 10:36 ` Paul Durrant
2017-06-07 11:06 ` Paul Durrant
2017-06-07 11:57 ` Juergen Gross
2017-06-07 12:02 ` Paul Durrant
2017-06-07 12:13 ` Juergen Gross
2017-06-07 12:19 ` Jan Beulich
2017-06-07 12:26 ` Paul Durrant
2017-06-07 12:34 ` Jan Beulich
2017-06-07 11:50 ` Jan Beulich
2017-06-07 11:55 ` Paul Durrant
2017-06-07 12:00 ` Jan Beulich
2017-06-07 12:46 ` Paul Durrant
2017-06-07 12:55 ` Jan Beulich
2017-06-07 15:06 ` Paul Durrant [this message]
2017-06-07 15:33 ` Jan Beulich
2017-06-07 15:40 ` Paul Durrant
2017-06-07 15:52 ` Jan Beulich
2017-06-08 12:42 ` Paul Durrant
2017-06-08 12:46 ` Juergen Gross
2017-06-08 13:18 ` Jan Beulich
2017-06-08 13:24 ` Paul Durrant
2017-06-09 12:19 ` Paul Durrant
2017-06-09 13:05 ` Jan Beulich
2017-06-09 13:52 ` Boris Ostrovsky
2017-06-09 15:14 ` Paul Durrant
2017-06-09 15:41 ` Jan Beulich
2017-06-09 15:47 ` Paul Durrant
2017-06-09 15:58 ` Jan Beulich
2017-06-12 8:14 ` Paul Durrant
2017-06-12 10:40 ` Jan Beulich
2017-06-12 10:44 ` Paul Durrant
2017-06-12 10:53 ` Paul Durrant
2017-06-12 11:12 ` Jan Beulich
2017-06-12 12:05 ` Paul Durrant
2017-06-12 12:25 ` Paul Durrant
2017-06-12 13:54 ` Jan Beulich
2017-06-12 14:28 ` Paul Durrant
2017-06-12 14:43 ` Paul Durrant
2017-06-12 15:03 ` Paul Durrant
2017-06-12 15:07 ` Jan Beulich
2017-06-12 15:21 ` Paul Durrant
2017-06-06 17:40 ` Julien Grall
2017-06-07 8:05 ` Paul Durrant
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=ee93e45315794a3db4aa21beefb62e52@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.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).