← previous next →
Pages: [1]

Author Topic: Qemu-i386  (Read 26135 times)

Borealid

  • Newbie
  • *
  • Posts: 46
    • View Profile
Qemu-i386
« on: September 06, 2005, 08:40:14 pm »
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?
Logged

Borealid

  • Newbie
  • *
  • Posts: 46
    • View Profile
Qemu-i386
« Reply #1 on: September 17, 2005, 04:26:30 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.
Logged

malik

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Qemu-i386
« Reply #2 on: September 29, 2005, 11:54:12 am »
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=96135\"][{POST_SNAPBACK}][/a][/div]


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
Logged
borzoi, cacko 1.23 lite, 1gb kingston cf, 512mb toshiba sd.. suse 10.0

Borealid

  • Newbie
  • *
  • Posts: 46
    • View Profile
Qemu-i386
« Reply #3 on: September 29, 2005, 05:44:13 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.
Logged

merli

  • Full Member
  • ***
  • Posts: 227
    • View Profile
    • http://
Qemu-i386
« Reply #4 on: September 30, 2005, 06:21:25 am »
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=97605\"][{POST_SNAPBACK}][/a][/div]
Can you share your good work with us and put your binaries anf howto somewhere on web? Thank you ...
Logged
merli
------
SL-C1000 - pdaxii13 5.3.3 but considering go back to beta1
Wifi D-link DCF-650W CF card - not using
bluetooth Billionton BT CF card and Samsung SGH-i310 GPRS
Pretec Cheetah 133x 4GB SD, Pretec Cheetah 80x 1GB CF

Borealid

  • Newbie
  • *
  • Posts: 46
    • View Profile
Qemu-i386
« Reply #5 on: September 30, 2005, 06:45:48 am »
Here is the Qemu binary.  Enjoy it.
Logged

Borealid

  • Newbie
  • *
  • Posts: 46
    • View Profile
Qemu-i386
« Reply #6 on: September 30, 2005, 06:48:53 am »
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.
Logged

malik

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Qemu-i386
« Reply #7 on: October 04, 2005, 10:11:09 am »
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;-)
Logged
borzoi, cacko 1.23 lite, 1gb kingston cf, 512mb toshiba sd.. suse 10.0

Borealid

  • Newbie
  • *
  • Posts: 46
    • View Profile
Qemu-i386
« Reply #8 on: October 04, 2005, 01:26:29 pm »
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.
Logged

malik

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Qemu-i386
« Reply #9 on: October 06, 2005, 10:24:50 am »
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
Logged
borzoi, cacko 1.23 lite, 1gb kingston cf, 512mb toshiba sd.. suse 10.0

Stubear

  • Hero Member
  • *****
  • Posts: 1164
    • View Profile
    • http://
Qemu-i386
« Reply #10 on: October 06, 2005, 08:41:45 pm »
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
Logged
SL-C1000, Hand converted to English with Japanese Input
Running X apps via X/Qt
iRiver USB host cable; Diatec P-Cord usb power cable (extendable); Acro's Reel Cable USB (A to A, B, Mini-B,  & Mini-B 8pin); GreenHouse 1Gb PicoDrive+; 2x256Mb Hagiwara SD cards; 128Mb Transcend CF card; 512Mb PQI CF card; AmbiCom WL1100C-CF 11B WLAN card

Borealid

  • Newbie
  • *
  • Posts: 46
    • View Profile
Qemu-i386
« Reply #11 on: October 07, 2005, 06:57:17 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.
Logged

malik

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Qemu-i386
« Reply #12 on: October 09, 2005, 04:42:27 pm »
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=98531\"][{POST_SNAPBACK}][/a][/div]

                                  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
Logged
borzoi, cacko 1.23 lite, 1gb kingston cf, 512mb toshiba sd.. suse 10.0

malik

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Qemu-i386
« Reply #13 on: October 09, 2005, 05:03:09 pm »
i have to apologize. first i should read the whole thread and then write
something that makes more sense than the above:-) sorry...
Logged
borzoi, cacko 1.23 lite, 1gb kingston cf, 512mb toshiba sd.. suse 10.0

malik

  • Full Member
  • ***
  • Posts: 149
    • View Profile
Qemu-i386
« Reply #14 on: February 28, 2006, 05:41:23 am »
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
Logged
borzoi, cacko 1.23 lite, 1gb kingston cf, 512mb toshiba sd.. suse 10.0
Pages: [1]
← previous next →