Help - Search - Members - Calendar
Full Version: Qemu-i386
OESF Forums > Distros, Development, and Model Specific Forums > Everything Development > Linux Applications
Borealid
Applying the gist of the changes from this message, I have successfully built a qemu-i386 and qemu-img binary on my Zaurus SL-C3100 (inside a Debian chroot).

I hoped to use it to launch wine in user mode, so I grabbed the full i386 deptree of Debian's testing Wine distribution and ran "dpkg -x --instdir=/x86" on each .deb, creating a tree that (theoretically) contains all the x86 binaries and libs that wine needs to run. However, I following Qemu's user-mode documentation, I tried to run /x86/usr/bin/yes and get:

"Unable to load interpreter
Segmentation fault"

The program is able to display its --help just fine.

I'm not at all familiar with cross-compilation and such, which is why I went for the prepackaged i386 environment instead of rolling my own glibc; is the problem there, or is the qemu executable I built somehow bad?

I'd love to get qemu-i386 and wine working together on the Z, and it seems tantalizingly close to possibility... It should be working now, in theory.

Is there any help out there?
Borealid
If anyone's interested, I eventually got it to work by using Qemu's own gnemul package. It runs an x86 ls, but takes around 30 seconds to do it. That's not worthwhile, yet. I can run Wine, but it's way too slow.
malik
QUOTE(Borealid @ Sep 17 2005, 08:26 PM)
If anyone's interested, I eventually got it to work by using Qemu's own gnemul package.  It runs an x86 ls, but takes around 30 seconds to do it.  That's not worthwhile, yet.  I can run Wine, but it's way too slow.
*



hi there, i am interested:-) tell me more details please on running wine on the zaurus.
i use wine and qemu on the desktop, but thought that it would be nearly "impossible"
to run them on the z...

malik
Borealid
Well, I built Qemu from source (using the listed patches' changes in spirit and only selecting the qemu-i386 target [no kqemu]), and installed their gnemul-x86 package. I then went and fetched Debian's Wine and all its dependencies from their ARM distribution. But really, it's too slow - it takes a half-minute to run ls. You wouldn't be able to get anything at all done with Wine. I know it's really alluring, but it's just not good enough.
merli
QUOTE(Borealid @ Sep 29 2005, 11:44 PM)
Well, I built Qemu from source (using the listed patches' changes in spirit and only selecting the qemu-i386 target [no kqemu]), and installed their gnemul-x86 package.  I then went and fetched Debian's Wine and all its dependencies from their ARM distribution.  But really, it's too slow - it takes a half-minute to run ls.  You wouldn't be able to get anything at all done with Wine.  I know it's really alluring, but it's just not good enough.
*

Can you share your good work with us and put your binaries anf howto somewhere on web? Thank you ...
Borealid
Here is the Qemu binary. Enjoy it.
Borealid
Oops. heh - attachments with (without) certain extensions are not allowed. Please eliminate the extension on this file. It's not really an .ipk but a .tgz.
malik
thank you for the ipk, i also found qemu-0.5.3-armhost-i386user.tar.gz out there,
but i cant find a debian arm version of wine. if wine works within pocketworkstation
i would give it a try, just for fun;-)
Borealid
Wine is an x86-only program. There's no such thing as an "arm version" at the moment. That's why there's so much experimentation with qemu and bochs going on out there.
malik
okay, i think i am on the right way: you use qemu on your z to run a
linux version of wine? this is somewhat crazy:-) i am a little bit dissapointed that
there is no arm version of wine and that qemu only runs in user mode...

malik
Stubear
There is no arm version of wine, because "Wine Is Not an Emulator"! It uses native x86 cpu calls and just translates the windows api calls to display graphics.

It's possible that winw would work under qemu, but the performance hit would probably be very high and I've had little success with qemu on sharp with graphic stuff

Stu
Borealid
I believe that Wine under qemu would probably be a superior solution to a full Windows environment under bochs or the like. Not having the massive overhead of a complete Windows implementation might be helpful.

But either way, it requires CPU emulation - either qemu or bochs.
malik
QUOTE(Borealid @ Oct 7 2005, 10:57 AM)
I believe that Wine under qemu would probably be a superior solution to a full Windows environment under bochs or the like.  Not having the massive overhead of a complete Windows implementation might be helpful.

But either way, it requires CPU emulation - either qemu or bochs.
*


hello borealid,

sorry, but i have problems with your ipk. first it is not a real ipk, its a *.tar.gz.
this is not the problem. i unpacked it and ran the binary (qemu --help), that works,
but it does not work if i apply it to a linux binary, for instance a simple hello program.
i have a working, but old version of qemu (0.5.3). any hints? i install the gnemul package
(i386 libraries) from the qemu homepage to /usr/gnemul. which libraries you
installed to start wine with qemu? thank you for your help...

malik
malik
i have to apologize. first i should read the whole thread and then write
something that makes more sense than the above:-) sorry...
malik
hello,

i want to report my similar experiences with qemu onboard compilation:

i also applied the above mentioned patches to the sources of qemu 0.7.1 resp.
0.8 and compiled within pocket workstation. first i got some reference errors in
block.c, so i commented out the last lines of it resp. changed the Makefile.
a step by step compilation (starting without the patches) showed that all patches
seem to be necessary, but the result is n both cases an unbelievable slow
qemu-i386 binary. i was not able to compile a static version.

i was only confused by the different debian packages for sdl and that compared
to my linux desktop "sdl static link" was not available.

maybe i will try to compile within dev-img1.5 or cross compile it. but first i
have to setup these, for instance how can i add libsdl-dev to dev-img?!

malik
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.