From: Benito <benito@itcsnam.com>
To: qemu-devel@nongnu.org
Cc: mjt@tls.msk.ru,
"\"afaerber@suse.de >> Andreas Färber\"" <afaerber@suse.de>
Subject: [Qemu-devel] Fwd: Re: Raspberry ARM with 32-bit guest
Date: Thu, 04 Apr 2013 16:06:11 +0200 [thread overview]
Message-ID: <515D88D3.5000203@itcsnam.com> (raw)
In-Reply-To: <515D755A.7060500@itcsnam.com>
[-- Attachment #1: Type: text/plain, Size: 3012 bytes --]
Ok , I do have a qemu-system-i386 :
pi@raspberrypi / $ qemu-system-i386 --version
QEMU emulator version 1.1.2 (Debian 1.1.2+dfsg-6a), Copyright (c)
2003-2008 Fabrice Bellard
My intention is to run an old application , that used to run on
FedoraCore2,also a modified version of the app runs on Centos 5.1/6.3
also Fedora 14 .
The problem lies with glibc. The glibc in newer kernels , is backwards
compatible up to a certain point, but not far enough. The version I
require is GLIBC.2.0
also, the app never ran on debian , always fedora/Red hat and Centos ,
hence the emulation of i386 on ARM. So it requires ld-linux.so.2 ,
libc.so.6 and so on.
The RPM Package for glibc-2.12.90-1mgc25.i686.rpm , is the package for
fc14. - in the /lib directory of FC14 :
[root@mdr lib]# ls -al libc.so.6
lrwxrwxrwx. 1 root root 15 Oct 22 2010 libc.so.6 -> libc-2.12.90.so
Now there are only a few of these libraries, like /lib/ld-linux.so.2
/lib/libm.so.6 that are needed to run.
Do you mean there's a possibility that I'd be able to run the libraries,
via the qemu-i386 and
manage to get the app working? Also should i try and use
qemu-system-i386 and try it the same way I did with only qemu?
I have a Model B pi, 512 MB RAM ,Disk space : rootfs 3.6G 2.0G 1.5G
57% / (the puppy iso is 130 MB , the centos one is +- 300 ) This should
suffice right ?
Thank you so much for your response
Regards
> Hi,
>
> Am 04.04.2013 13:06, schrieb Benito:
>> I know this might absurd, but
>> I'm trying to run a 32-bit guest on a Raspberry Pi - Raspbian OS -
>> Debian Wheezy ARM
>> I have used :
>>
>> qemu-img create -f raw harddrive.raw 700M
>> qemu -hda harddrive.raw -cdrom fedora14.iso
>>
>> I've installed qemu via apt-get install qemu on the Pi.
> You're not providing sufficient details for the upstream community to
> help you, so CC'ing the Debian maintainer. "qemu" sounds rather old,
> it's qemu-system-i386 since several versions already.
>
> Did you check that you have sufficient RAM on your Raspi? Or disk space
> on your SD card / USB disk? Disk images are created sparse, and when the
> host runs out of resources lots of things can happen.
>
>> After I do the 2nd command, the guest os starts up , but soon consumes
>> 100% cpu , and then hangs. Tried with puppy 511 , centos6.3 minimal ,
>> fedora14
>>
>> Is there a way to run any of these in "invisible" mode or user mode ,
>> and get past this obstacle.. ?
> qemu-i386 can execute individual Linux binaries, with a bunch of known
> issues. Might or might not work for you - you don't say what you
> actually want to do.
>
>> Can I create this guest on a faster machine , and clone itto the Pi's
>> qemu that runs ARM ?
> Yes. The disk image is just a file.
>
> Regards,
> Andreas
>
>> Also am I missing something regarding the creation of the guest? I don't
>> need a GUI for the guest, just need to be able to get to it and execute
>> commands.
>> Please could someone point me in the right direction ?
>>
>> Kind Regards
>> Benito
[-- Attachment #2: Type: text/html, Size: 4313 bytes --]
next parent reply other threads:[~2013-04-04 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <515D755A.7060500@itcsnam.com>
2013-04-04 14:06 ` Benito [this message]
2013-04-04 14:27 ` [Qemu-devel] Fwd: Re: Raspberry ARM with 32-bit guest Peter Maydell
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=515D88D3.5000203@itcsnam.com \
--to=benito@itcsnam.com \
--cc=afaerber@suse.de \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.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).