From: Peter Maydell <peter.maydell@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Niccolò Belli" <darkbasic@linuxsystems.it>,
"open list:sPAPR" <qemu-ppc@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ELF load command alignment not page-aligned
Date: Tue, 17 Sep 2019 12:40:22 +0100 [thread overview]
Message-ID: <CAFEAcA94_kJ=5ABvB6B11U5NKpxka7e11tkB46m7qSMBFQQW9A@mail.gmail.com> (raw)
In-Reply-To: <9d1ea4ff-a0df-f7c6-54ca-c03b010c5ff1@redhat.com>
On Tue, 17 Sep 2019 at 11:49, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>
> Cc'ing PPC folks and Laurent.
>
> On 9/16/19 11:06 PM, Niccolò Belli wrote:
> > Hi,
> > I'm trying to use qemu-user-static to chroot into a foreign amd64
> > environment from my ppc64le host.
> > The host has a 64k page size, while x86_64 uses 4k.
> > I get those errors while loading shared libraries: "ELF load command
> > alignment not page-aligned"
> > Is there any way to fix this? I cannot simply switch to 4k page size
> > because my btrfs filesystem won't mount anymore (it requires the
> > sectorsize to be equal to the page size).
I vaguely recall that the answer is that we don't really
support running a linux-user guest which has a smaller page
size than the host. There are some sort-of-hacks in the code,
so some simple cases might more-or-less work, but I'm not
very surprised that you've run into something that doesn't
work.
Cc:ing Richard who probably has a more accurate answer.
thanks
-- PMM
next prev parent reply other threads:[~2019-09-17 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 21:06 [Qemu-devel] ELF load command alignment not page-aligned Niccolò Belli
2019-09-17 10:33 ` Philippe Mathieu-Daudé
2019-09-17 10:40 ` Laurent Vivier
2019-09-17 11:09 ` Niccolò Belli
2019-09-17 11:35 ` Laurent Vivier
2019-09-17 11:40 ` Peter Maydell [this message]
2019-09-17 19:12 ` Richard Henderson
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='CAFEAcA94_kJ=5ABvB6B11U5NKpxka7e11tkB46m7qSMBFQQW9A@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=darkbasic@linuxsystems.it \
--cc=lvivier@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.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).