From: Manuel Bouyer <bouyer@antioche.eu.org>
To: Juergen Gross <jgross@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: issue with dom0_pvh on Xen 4.20
Date: Tue, 2 Sep 2025 15:41:55 +0200 [thread overview]
Message-ID: <aLb0I01WASpFremM@mail.soc.lip6.fr> (raw)
In-Reply-To: <2ad255ea-6c5e-4e9a-a821-db7449432399@suse.com>
On Tue, Sep 02, 2025 at 02:28:27PM +0200, Juergen Gross wrote:
> > What puzzles me is that:
> >
> > - %cr2 is 0, so probably the first fault wasn't a page fault
> > - RIP is %ebx + 8, so maybe the code was just clobbered by the loop?
> >
> > Could it be the code has been moved to this location, or is about to
> > be moved away afterwards?
>
> And indeed: from the full boot log I can see:
>
> (XEN) virt_base = 0x0
> (XEN) elf_paddr_offset = 0x0
> (XEN) virt_offset = 0x0
> (XEN) virt_kstart = 0x200000
> (XEN) virt_kend = 0x17bab90
> (XEN) virt_entry = 0x20e4d0
>
> So virt_kentry is very near to the RIP.
thanks to this, I think I found the issue:
with Xen 4.18, the kernel is started with ebx=17bb018; with 4.20 it's
100018.
The bootstrap code assumes that the kernel is after the kernel, and the
kernel symbol table. That seems to be no longer true with Xen 4.20 and a
PVH dom0 (but probably still true in all other cases).
I can deal with that, but with the new layout how do I get the end of the
symbol table ?
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--
next prev parent reply other threads:[~2025-09-02 13:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 10:17 issue with dom0_pvh on Xen 4.20 Manuel Bouyer
2025-09-02 10:44 ` Andrew Cooper
2025-09-02 10:56 ` Manuel Bouyer
2025-09-02 11:13 ` Andrew Cooper
2025-09-02 11:23 ` Manuel Bouyer
2025-09-02 12:14 ` Andrew Cooper
2025-09-02 12:24 ` Manuel Bouyer
2025-09-02 12:52 ` Andrew Cooper
2025-09-02 12:55 ` Andrew Cooper
2025-09-02 12:56 ` Manuel Bouyer
2025-09-02 12:00 ` Jan Beulich
2025-09-02 12:10 ` Manuel Bouyer
2025-09-02 12:54 ` Jan Beulich
2025-09-02 12:22 ` Juergen Gross
2025-09-02 12:28 ` Juergen Gross
2025-09-02 12:49 ` Manuel Bouyer
2025-09-02 13:41 ` Manuel Bouyer [this message]
2025-09-02 13:55 ` Jan Beulich
2025-09-02 14:06 ` Manuel Bouyer
2025-09-02 14:23 ` Jan Beulich
2025-09-02 14:28 ` Manuel Bouyer
2025-09-02 14:32 ` Manuel Bouyer
2025-09-02 13:58 ` Andrew Cooper
2025-09-02 12:28 ` Manuel Bouyer
2025-09-02 12:45 ` Jan Beulich
2025-09-02 12:54 ` Manuel Bouyer
2025-09-02 12:56 ` Jan Beulich
2025-09-02 13:05 ` Manuel Bouyer
2025-09-03 15:47 ` Manuel Bouyer
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=aLb0I01WASpFremM@mail.soc.lip6.fr \
--to=bouyer@antioche.eu.org \
--cc=andrew.cooper3@citrix.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 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.