From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BdB24-00036a-9a for qemu-devel@nongnu.org; Wed, 23 Jun 2004 12:55:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BdB22-00034D-FG for qemu-devel@nongnu.org; Wed, 23 Jun 2004 12:55:31 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BdB22-00033o-C3 for qemu-devel@nongnu.org; Wed, 23 Jun 2004 12:55:30 -0400 Received: from [38.113.3.61] (helo=babyruth.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BdAzx-00035j-As for qemu-devel@nongnu.org; Wed, 23 Jun 2004 12:53:21 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by babyruth.hotpop.com (Postfix) with SMTP id A657963C3E8 for ; Wed, 23 Jun 2004 16:13:04 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp03144805pcs.midval01.tn.comcast.net [68.59.228.236]) by smtp-3.hotpop.com (Postfix) with ESMTP id B6F3BFA6978 for ; Wed, 23 Jun 2004 16:37:33 +0000 (UTC) Date: Wed, 23 Jun 2004 12:50:06 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1) Message-ID: <20040623165006.GA22835@jbrown.mylinuxbox.org> References: <200406230805.16198.dcuny@lanset.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200406230805.16198.dcuny@lanset.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Wed, Jun 23, 2004 at 08:05:16AM -0400, David wrote: > 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 > That is not exactly true. Qemu works fine for me, even when I start it when I am offline. However I use VDE/tuntap and do have a local area network, so it is possible that qemu requires a network connection to function correctly (IIRC since 0.5.5 qemu uses -user-net by default if it can not access tuntap, and -dummy-net by default for earlier versions). Of course tuntap requires that you have an actual ethernet card to work.... BTW if you are using the Windows port, you might be better off using -dummy-net or -user-net ... I vaguely recall that one of the reasons -user-net was introduced was because it was so hard to set up networking with qemu when Windows was the host OS. > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.