Interesting stuff.
With 0.14 and 1.2
wineserver will run if you say wineserver -d2 -f -p for example.
I believe it is forking when you run plain old wineserver because it really is
getting an invalid argument.
I am running Wine 1.1.14 and Qemu 0.14 and I can run many apps.
I cannot run a
Does this have anything to do with Memory Mapping? I have a feeling it
does
I notice the mmap_min_addr setting for arm is 4096
For x86 its 65536
http://www.onsitedentalsystems.com/error.jpg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
The app I am testing does run on qemu-i386 compiled for x86.. and the
host is x86.
The screen shot I posted in the last post is what happens when you run
qemu and wine on arm instead of qemu and wine on x86.
--
You received this bug notification because you are a member of qemu-
devel-ml,
So this is a compiler or system header error?
Anybody examined the differences in code generated with native compiler
and crosscompiler?
Is there some code difference or are wrong kernel headers pulled from
i386 resulting in invalid syscalls?
--
You received this bug notification because you
Michal Suchanek wrote:
So this is a compiler or system header error?
Anybody examined the differences in code generated with native compiler and
crosscompiler?
...this comment doesn't make much sense to me -- did you add it to the
wrong bug report by mistake? i386 user mode's issues are not
It might be just coincidence but if you read the above comments you will
notice that people who compiled qemu natively on arm report that they
can run various binaries without issue but people who crosscompiled
report that they can't run the simplest i386 shell utilities.
How come that the
I do now know... I compile on my phone and tablet. In fact I loaded
Ubuntu on my Touchpad last night, native.
http://code.google.com/p/hp-touchpad-ubuntu/wiki/Installation
No more chroot to deal with.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
How come that the functionality that is missing magically appears for
some people?
Coincidence. Nobody on this bug report has reported that they've been
able to run x86 binary X with a native compiled qemu but not with a
cross compiled version of the same qemu sources. I think it is vastly
more
I am now able to run winecfg... you have to have wine-pthread run winecfg
qemu-i386 /usr/bin/qemu-i386 wine-pthread winecfg
All the tabs load except audio.. For that it hangs..
Trying to fix that.. I want to run an app that hangs and it uses audio.
--
You received this bug notification because
how to run without binfmt support in the kernel.
/usr/bin/qemu-i386 /usr/bin/wineserver
/usr/bin/qemu-i386 /usr/bin/wine-pthread notepad.exe
or
/usr/bin/qemu-i386 -L /usr/gnemul/qemu-i386 /usr/bin/wineserver
/usr/bin/qemu-i386 -L /usr/gnemul/qemu-i386 /usr/bin/wine-pthread notepad.exe
If you do
HOW TO COMPILE ON ARM AND UBUNTU 12.04
This will run wine if you compile with 0.13 or 0.14
sudo apt-get install zlib1g-dev
sudo apt-get install libsdl1.2-dev
./configure --target-list=i386-linux-user --enable-sdl --prefix=/usr
--cross-prefix=arm-linux-gnueabi- --host-cc=gcc4.6
@Ricardo I did not have such a problem and it ran all simple programs just fine
(top, ls, cd, cp and so on) on my armv5t. Though I did not cross-compile, but
natively compiled qemu on the box itself.
It would be cool to have it working, but I don't think it will happen any time
soon. I just
@Peter - thanks, fair enough... I don't know enough about qemu's source
to understand what you mean, but clearly it's a complex issue. For now
the patch seems to work for me-- I haven't had the issue that @Ricardo
discusses (again, I'm on armv7l, though).
--
You received this bug notification
Just to give some support to what Peter said, here is my experience with
the patch from #32.
I cross-compiled qemu 0.14.1 with the patch to ARMv5 and tried to run
the i386 linux binary for dropbox. Although I no longer see the fork
error message, the process gets stuck in an infinite loop running
This bug also pertains to armv7l. I have a Debian chroot install on my
Android phone, and was trying to do an i386 chroot within my chroot
(want to run the i386 specific binaries included in the Android SDK).
I installed the qemu-user-static package (tried both v 0.14.1 and
0.15.0).
When
Steve: there are a number of issues with that patch:
* x86 cpu_set_tls() doesn't belong in linux-user/syscall.c (but it's not
trivial to put it in target-i386 because it's calling do_set_thread_area())
* it's not obviously correct and the author says it needs review, and I'd
have to dig out
Something odd. I installed VMWare with Ubuntu 11.04. Then I installed
wine and qemu with apt-get. Same exact errors using qemu-i386. Verbatim.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
No armel at all in #44. Perhaps if qemu cant run wine with user
emulation using x86.. it will not be able to do arm as well?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386
Just wanted to mention that the patch in comment #32 worked for me also.
I had to use the qemu-0.14.1.tar.gz source as mentioned in comment #34.
On 0.15.0 I did not get a compile error, but when it ran I still
couldn't fork.
--
You received this bug notification because you are a member of qemu-
I had exactly the same behavior with a patched 0.14.1. Wine doesn't work
and that was the reason I was so eager to run qemu.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386
Moonman, you know what I realized. I have the posix version of wine
running okay with qemu-i386... But I have never been able to compile my
own working version.. I realized that last night. I can compile, and it
will run, but wine never actually runs, and Im compiling with --enable-
sdl and all
See this can run the posix wine.. But I cant recreate it. Its running
qemu-0.12.2 which you can download and compile but I still cant get it
to play solitaire like I can with the one below.
wget http://a.trap.me.uk/qemu-i386
--
You received this bug notification because you are a member of
Okay I found that 12.5 I can run posix wine and that is compiling on my
own. gonna try the patch on 12.5 to see if it can run dynamic nptl
binaries
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Odd.. If I do ./configure --static --enable-sdl --target-list=i386
-linux-user this will work fine with 12.5 but on say 15 it cant find
SDL. I am on 1.2.13 I think.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/855630
I decided to give it, its own bug.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode on ARMv5 host fails
I would like to run wine. I have compiled qemu 0.15.5 from git and I
noticed we can enable nptl without a patch. I can run an x86 nptl bash
but I havent tried to chroot. I have the posix wine running with qemu...
So i tried it with wine and I am able to get a --version out of it, but
when I
Here is a strace.. fumex calls???
strace -ff -o /ls-strace-alignment-6.log /usr/bin/qemu-i386 /usr/bin
/wine-pthread notepad.exe
** Attachment added: wine.log
https://bugs.launchpad.net/qemu/+bug/739785/+attachment/2426371/+files/wine.log
--
You received this bug notification because you
Further research shown that the issue is that NPTL (Native Posix Threads) is
not supported for i386 user mode emulation.
That causes the described issue in binaries compiled with NPTL (most modern
ones).
One way to fix this that worked for me is a patch from here:
Awesome Artyom! I'm compiling now. I will report back if this patch
works for arm as well.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode on ARMv5 host fails
YES! That did the trick!
Though, with this patch I was unable to compile qemu 0.15rc1. I suppose
the patch wasn't meant for it, but with 0.14.1 it works flawlessly.
Also, I had to do echo 2 /proc/cpu/alignment as was mentioned by Peter.
I hope the patch gets applied to the main tree.
--
You
I have the same exact problem on MIPSel host as well.
Tried Qemu 0.14.1 and git from 110724.
Trying to run something from bash gives fork: Invalid argument.
strace gives clone(18874385,0,0,0,1084164376,1082144312) = -1 errno=22 (Invalid
argument)
There is no alignment switches on this CPU.
So,
I hope this can work so development for Dropbox on Drobo-FS can
continue
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode on ARMv5 host fails (bash: fork:
I have to add that it's with kernel 2.6.39 and qemu 0.14.1 compiled from
source
[root@Plugbox ~]# uname -a
Linux Plugbox 2.6.39-ARCH #1 PREEMPT Tue Jun 14 15:55:01 MDT 2011 armv5tel
Feroceon 88FR131 rev 1 (v5l) Marvell SheevaPlug Reference Board GNU/Linux
[root@Plugbox ~]#
Same here. The workaround does not work on a DroboFS, since it was
actually the default setting all along.
root@DroboFS:~# cat /proc/cpu/alignment
User: 74283231
System: 0
Skipped:0
Half: 0
Word: 74283231
DWord: 0
Multi: 0
User
OK, that's pretty conclusive. My initial theory about what's going on
here can't be right -- I'll investigate further.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user
Did you modify some code to get it working on your armv5 ?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode on ARMv5 host fails (bash: fork: Invalid argument)
** Attachment added: ls-strace-alignment-2.log.15427
https://bugs.launchpad.net/qemu/+bug/739785/+attachment/2170433/+files/ls-strace-alignment-2.log.15427
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Garbled text might have been fixed in the recent versions as it seems.
Even with User faults == 0 the text is not garbled.
[root@Plugbox ~]# strace -ff -o ls-strace.log chroot /i386 /usr/bin/qemu-i386
/bin/ls
Inconsistency detected by ld.so: dl-version.c: 230: _dl_check_map_versions:
Assertion
No, I just wrote a simple test program to check the thing I thought was
the problem (unaligned accesses). Do you still see the mangled text
problems you describe earlier in the bug report as well as the 'fork:
invalid argument' problem? I've reproduced the fork error message, but
not the mangled
[root@Plugbox ~]# strace -ff -o bash-strace-alignment-2.log chroot /i386
/usr/bin/qemu-i386 /bin/bash
[root@Plugbox /]# ls
bash: fork: Invalid argument
[root@Plugbox /]# exit
exit
** Attachment added: bash-strace-alignment-2.log.16325
Ok, it seemed as though ls worked from strace -ff -o ls-strace-
alignment-2.log chroot /i386 /usr/bin/qemu-i386 /bin/ls
so I tried to execute the package manager:
[root@Plugbox ~]# chroot /i386 /usr/bin/qemu-i386 /usr/bin/pacman -Suy
qemu: Unsupported syscall: 240
:: Synchronizing
If you need an i386 chroot for testing, I created one a while ago
(archlinux): http://www.mediafire.com/download.php?qq63mnay2byqqie
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
I think you should be able to work around this with:
echo 2 /proc/cpu/alignment
which makes unaligned accesses fault and the kernel fix them up. This
will be slower than if qemu wasn't generating unaligned accesses in the
first place but it should at least make things run. (echo 0 ... will
give
Hmm, it does not seem to work for me:
[root@Plugbox cpu]# cat alignment
User: 73412
System: 1
Skipped:0
Half: 5312
Word: 68091
DWord: 1
Multi: 0
User faults:2 (fixup)
[root@Plugbox cpu]# cd /i386/
[root@Plugbox i386]# chroot .
Neither does it work for me:
[root@Plugbox /]# cat /proc/cpu/alignment
User: 293831
System: 1
Skipped:0
Half: 22200
Word: 271546
DWord: 1
Multi: 0
User faults:2 (fixup)
[root@Plugbox /]# chroot /i386
[root@Plugbox /]# ls
bash:
It's only user-mode that doesn't work, I think
You are correct in saying that only user mode does not work. I did
install windows 98 in qemu VM and it worked fine (aside from the fact
that it was slow :))
--
You received this bug notification because you are a member of qemu-
devel-ml, which
Peter,
Am 29.03.2011 um 00:09 schrieb Peter Maydell:
Short answer: looks like QEMU doesn't currently work on ARMv5 hosts
(although ARMv7 are fine). I'll look into this if I can manage to
scare up some suitable hardware.
I noticed that configure prints any ARM host as armv4l. As an
interim
On 29 May 2011 11:19, Andreas Färber andreas.faer...@web.de wrote:
Am 29.03.2011 um 00:09 schrieb Peter Maydell:
Short answer: looks like QEMU doesn't currently work on ARMv5 hosts
(although ARMv7 are fine). I'll look into this if I can manage to
scare up some suitable hardware.
I noticed
Do you think it will ever get fixed in a reasonable amount of time
(or ever)
Well, it's on my list of things to look at, but generally my focus is
the current (ARMv7) architecture, and fixing ARMv5 only bugs is lower
priority. But there's a pretty good chance I'll get to it somewhere in
the next
But there's a pretty good chance I'll get to it somewhere in the next
few months.
That would be amazing. I've got a Linkstation Live v2 and a Drobo FS
waiting eagerly for the possibility of running some x86 binaries.
--
You received this bug notification because you are a member of qemu-
Do you think it will ever get fixed in a reasonable amount of time (or
ever)
Well, it's on my list of things to look at, but generally my focus is
the current (ARMv7) architecture, and fixing ARMv5 only bugs is lower
priority. But there's a pretty good chance I'll get to it somewhere in
the next
Do you think it will ever get fixed in a reasonable amount of time(or
ever) or am I better off just getting an x86 low power board to run x86
binary-only code?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
I'm afraid not, no.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode on ARMv5 host fails (bash: fork: Invalid argument)
Status in QEMU:
New
Bug description:
Hi,
Just wondering if there has been any progress regarding this issue.
Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Title:
qemu-i386 user mode on ARMv5 host fails (bash: fork:
** Summary changed:
- qemu-i386 on ARM bash: fork: Invalid argument
+ qemu-i386 user mode on ARMv5 host fails (bash: fork: Invalid argument)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/739785
Wow you are fast!
The hardware I use is pogoplug with plugapps linux. I think any plug computer
will do.
http://plugapps.com/index.php5/Install_on_Pogoplug_V2_Pink
They are sold for about $50.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
56 matches
Mail list logo
