From: David <dcuny@lanset.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1)
Date: Wed, 23 Jun 2004 08:05:16 -0400 [thread overview]
Message-ID: <200406230805.16198.dcuny@lanset.com> (raw)
In-Reply-To: <s0d9478a.059@GW-FS1.SHANDS.UFL.EDU>
Speaking of adding things to the documentation, it would be helpful to mention
that Qemu *requires* a network connection (or a simulated one via
'--dummy-net').
I ran into this problem because I still used dialup. I couldn't find any
explanation for the error message I was getting in the documentation, or via
Google. However, the act of going online caused Qemu to start working, and
it finally dawned on me what the problem was...
Thanks!
-- David Cuny
next prev parent reply other threads:[~2004-06-23 15:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 13:03 [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1) Thomas Munn
2004-06-23 12:05 ` David [this message]
2004-06-23 16:50 ` Jim C. Brown
2004-06-23 19:22 ` John R. Hogerhuis
2004-06-24 6:36 ` Jean-Michel POURE
2004-06-24 9:08 ` Christof Petig
2004-06-24 21:48 ` John R. Hogerhuis
2004-06-23 15:12 ` Antony T Curtis
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=200406230805.16198.dcuny@lanset.com \
--to=dcuny@lanset.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).