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 at 100% CPU. When started with -strace, this is where it gets stuck:
This four line block gets repeated over and over again.
To the best of my knowledge, this is the same as the dreaded "unsupported syscall 240" error, just with fancier output. My feeling is that the patch only fixes some very small part of the problem.
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 at 100% CPU. When started with -strace, this is where it gets stuck:
clock_gettime( 0,1169900288, 135693248, 1,0,1169900372) = 0 4,FUTEX_ PRIVATE_ FLAG|FUTEX_ WAIT,1, 0x45bb4300, 0x081683f0, 135693296 ) = -1 errno=110 (Connection timed out) 1169900364, 0,0,1,142600008 ,1169900392) = 0 0,FUTEX_ PRIVATE_ FLAG|FUTEX_ WAKE,1, 0x081683f0, 0x087fe748, 142600008 ) = 0
futex(0x081683c
gettimeofday(
futex(0x081683f
This four line block gets repeated over and over again.
To the best of my knowledge, this is the same as the dreaded "unsupported syscall 240" error, just with fancier output. My feeling is that the patch only fixes some very small part of the problem.