From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BdDLh-0003m6-De for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:23:57 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BdDLf-0003lm-Jm for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:23:56 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BdDLf-0003lc-I0 for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:23:55 -0400 Received: from [216.254.0.202] (helo=mail2.speakeasy.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BdDJi-0004f9-Sh for qemu-devel@nongnu.org; Wed, 23 Jun 2004 15:21:55 -0400 Received: from dsl081-088-222.lax1.dsl.speakeasy.net (HELO [192.168.111.2]) ([64.81.88.222]) (envelope-sender ) by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Jun 2004 19:21:52 -0000 Subject: Re: [Qemu-devel] Clarification about qemu-fast (was segfaults in fc1) From: "John R. Hogerhuis" In-Reply-To: <20040623165006.GA22835@jbrown.mylinuxbox.org> References: <200406230805.16198.dcuny@lanset.com> <20040623165006.GA22835@jbrown.mylinuxbox.org> Content-Type: text/plain Message-Id: <1088018545.18992.508.camel@aragorn> Mime-Version: 1.0 Date: Wed, 23 Jun 2004 12:22:26 -0700 Content-Transfer-Encoding: 7bit Reply-To: jhoger@pobox.com, 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, 2004-06-23 at 09:50, Jim C. Brown wrote: > 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 The main reasons for -user-net are to: 1) Create no-configuration-required networking. Any guest OS which is set up to collect IP via DHCP should automatically have access to the network when run under QEMU (assuming the host has network access). 2) Not require any changes to OS which necessitate root access. Many users on Windows are not admin on their own machines, due to corporate network policies. One of these days we will see a autorun QEMU included on Knoppix disk which will load up Knoppix on insertion into any Windows PC.