From: "Andreas Färber" <afaerber@suse.de>
To: Bug 938945 <938945@bugs.launchpad.net>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 938945] [NEW] Slirp cannot be forward and makes segmentation faults
Date: Thu, 23 Feb 2012 16:25:49 +0100 [thread overview]
Message-ID: <4F465A7D.8080002@suse.de> (raw)
In-Reply-To: <20120222195009.30707.32438.malonedeb@chaenomeles.canonical.com>
Am 22.02.2012 20:50, schrieb Vincent Autefage:
> $ qemu -enable-kvm -name opeth -hda debian1.img -k fr -localtime -m 512
The qemu executable has been renamed to qemu-system-i386 some time ago.
Are you sure you're executing the right one, and which version are you
using? Did you check qemu.git master?
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-02-23 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 19:50 [Qemu-devel] [Bug 938945] [NEW] Slirp cannot be forward and makes segmentation faults Vincent Autefage
2012-02-23 15:25 ` Andreas Färber [this message]
2016-12-15 18:02 ` [Qemu-devel] [Bug 938945] " Thomas Huth
2017-02-14 4:17 ` Launchpad Bug Tracker
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=4F465A7D.8080002@suse.de \
--to=afaerber@suse.de \
--cc=938945@bugs.launchpad.net \
--cc=jan.kiszka@siemens.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).