Debian Bug report logs - #674201
/usr/bin/qemu-i386: fork() doesn't work

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Dan Greene <dan-greene@wi.rr.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: /usr/bin/qemu-i386: fork() doesn't work

Date: Wed, 23 May 2012 15:05:55 -0500

Package: qemu-user
Version: 1.0.1+dfsg-1
Severity: normal
File: /usr/bin/qemu-i386

Dear Maintainer,
When using qemu-i386 to run any program that tries to fork, the fork fails,
making many (perhaps most) programs unusable.

Here is an example (host is i386, so no chroot needed):
$ qemu-i386 /bin/bash
$ ls
bash: fork: Invalid argument
$ exit
exit

The expected behavior, of course, would be for ls to actually be executed.

Note that qemu-arm does not exhibit this bug, nor does qemu-i386 system.

(On i386, this bug doesn't hurt the usablility of this package, since it is
easier and faster to just run the program natively. But on other
architectures, this bug is a problem. In particular, one might want, for
example, to run WINE under qemu-i386 since it doesn't work on other
architectures.)

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages qemu-user depends on:
ii  libc6         2.13-32
ii  libglib2.0-0  2.32.3-1

qemu-user recommends no packages.

Versions of packages qemu-user suggests:
ii  sudo  1.8.3p2-1

-- no debconf information

Message #10 received at 674201@bugs.debian.org (full text, mbox, reply):

From: Matt Zimmerman <mdz@debian.org>

To: 674201@bugs.debian.org

Subject: /usr/bin/qemu-i386: fork() doesn't work

Date: Sat, 17 Nov 2012 13:50:02 -0800

I'm seeing the same problem.  There is a patch linked from
https://bugs.launchpad.net/qemu/+bug/739785/comments/32 which is reported to
fix the problem for some people.  The patch is at
http://patchwork.ozlabs.org/patch/45206/

-- 
 - mdz

Message #17 received at 674201@bugs.debian.org (full text, mbox, reply):

From: "Justin Shafer" <justinshafer@gmail.com>

To: <674201@bugs.debian.org>

Subject: Wine does run.. sort of

Date: Sun, 18 Nov 2012 07:32:36 -0600

[Message part 1 (text/plain, inline)]

I am trying to get a neobook file to run for olpc under fedora.. Same
problems as Ubuntu.

 

You can get wineserver and wine-pthread to run..

 

Wineserver -d2 -f -p will run, because all the switches are being called is
my guess.. 

 

If you run wine2002 or wine 0.9.20-1.1.14 and forget to call wineserver
first.. you can see that wine gripes about an unexpected character "("
without quotes.

 

My guess is wine is somehow receiving an "invalid argument" because if a
character that is wrong in the command. 

 

No idea why. I can run pinball, solitaire, but I cannot run explorer.exe..
the one built into wine. Even with binfmt. 

 

Right now I am compiling 0.9.20 on slackware 10.0 to see if neobook will run
and then try to copy everything over to arm.. If that doesn't work I am
going to try wine 2002.. It runs without any problems, besides X11.. no
syscalls or anything like that though.

 

 

[Message part 2 (text/html, inline)]

Message #24 received at 674201-done@bugs.debian.org (full text, mbox, reply):

From: Michael Tokarev <mjt@tls.msk.ru>

To: Dan Greene <dan-greene@wi.rr.com>, 674201-done@bugs.debian.org

Subject: Re: Bug#674201: /usr/bin/qemu-i386: fork() doesn't work

Date: Thu, 28 Nov 2013 00:08:43 +0400

Version: 1.6.0+dfsg-1

24.05.2012 00:05, Dan Greene wrote:
> Package: qemu-user
> Version: 1.0.1+dfsg-1
> Severity: normal
> File: /usr/bin/qemu-i386
> 
> Dear Maintainer,
> When using qemu-i386 to run any program that tries to fork, the fork fails,
> making many (perhaps most) programs unusable.
> 
> Here is an example (host is i386, so no chroot needed):
> $ qemu-i386 /bin/bash
> $ ls
> bash: fork: Invalid argument
> $ exit
> exit

This has been finally fixed in 1.6.0 version.  Closing this bugreport now.

Thanks,

/mjt

Send a report that this bug log contains spam.