From: Adam Nielsen <a.nielsen@shikadi.net>
To: Jeff Dike <jdike@addtoit.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>,
"LKML Mailinglist" <linux-kernel@vger.kernel.org>
Subject: Re: UML broken - runaway loop modprobe binfmt-464c
Date: Sun, 21 Feb 2010 13:00:02 +1000 [thread overview]
Message-ID: <4B80A1B2.10207@shikadi.net> (raw)
In-Reply-To: <20100215161111.GA18664@c2.user-mode-linux.org>
>> So you are using 32-bit modprobe binary and 64-bit kernel?
>>
>> This will not work, since kernel binfmt_elf module checks
>> if e_machine is EM_X86_64.
>
> Not just 32-bit modprobe - any 32-bit binary on a 64-bit UML will
> cause this, I think.
Thanks for the suggestions. After some more investigation and off-list
pointers, it seems the problem is caused because compiling UML for x86_64
doesn't allow you to enable IA32 emulation.
Is this just a case of the Kconfig option being missed, or is there a more
fundamental reason as to why, unlike with the Linux kernel, it's not possible
to run 32-bit apps inside a 64-bit UML?
Thanks,
Adam.
prev parent reply other threads:[~2010-02-21 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 6:47 UML broken - runaway loop modprobe binfmt-464c Adam Nielsen
2010-02-15 11:37 ` Américo Wang
2010-02-15 16:11 ` Jeff Dike
2010-02-21 3:00 ` Adam Nielsen [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=4B80A1B2.10207@shikadi.net \
--to=a.nielsen@shikadi.net \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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