From: "T. Huth" <788701@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 788701] Re: qemu-user fails to run rpcgen (i386, x86_64)
Date: Mon, 27 Jun 2016 20:51:18 -0000 [thread overview]
Message-ID: <20160627205120.18109.48290.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 20110526161532.13632.99231.malonedeb@gac.canonical.com
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/788701
Title:
qemu-user fails to run rpcgen (i386, x86_64)
Status in QEMU:
Fix Released
Bug description:
Confirmed on qemu current development tree (git commit aa29141). While
trying to run eglibc's rpcgen from native system by qemu-user, I get
an error:
qemu-x86_64 /usr/bin/rpcgen -c /dev/null
fork: Invalid argument
I am running a Debian Wheezy system and rpcgen comes from libc-dev-
bin. Just in case I am attaching my rpcgen binaries from i386 and
x86_64 systems.
Very similar problem was mentioned on the QEMU forum on February 2007,
so I guess it might be a known issue. Nevertheless, I was unable to
find any information about bug reports, fixes nor workarounds for it
so I'm reporting it here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/788701/+subscriptions
prev parent reply other threads:[~2016-06-27 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 16:15 [Qemu-devel] [Bug 788701] [NEW] qem-user fails to run rpcgen (i386, x86_64) Rafał Krypa
2011-05-26 16:15 ` [Qemu-devel] [Bug 788701] " Rafał Krypa
2011-05-26 16:28 ` [Qemu-devel] [Bug 788701] Re: qemu-user " Rafał Krypa
2013-07-26 12:45 ` Peter Maydell
2016-06-27 20:51 ` T. Huth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160627205120.18109.48290.launchpad@wampee.canonical.com \
--to=788701@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.