From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JMVMF-00029U-Jj
	for qemu-devel@nongnu.org; Tue, 05 Feb 2008 16:29:35 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JMVMD-00029A-4g
	for qemu-devel@nongnu.org; Tue, 05 Feb 2008 16:29:34 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JMVMC-000297-V9
	for qemu-devel@nongnu.org; Tue, 05 Feb 2008 16:29:33 -0500
Received: from mail.codesourcery.com ([65.74.133.4])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1JMVMC-0001Uj-NZ
	for qemu-devel@nongnu.org; Tue, 05 Feb 2008 16:29:33 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
Date: Tue, 5 Feb 2008 21:29:25 +0000
References: <20080205162206.38J1B.215136.root@eastrmwml22.mgt.cox.net>
In-Reply-To: <20080205162206.38J1B.215136.root@eastrmwml22.mgt.cox.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200802052129.26282.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org, sol10x86@cox.net
Cc: andreas.faerber@web.de, Asheesh Laroia <asheesh@creativecommons.org>

> > but make
> > it configurable on the command line.  That way, there are no surprises
> > ever.  The rare people like me with an issue can just pass a command-line
> > parameter in.
>
> The point I was trying to make is that qemu could easily arbitrate the
> guest network based on how the host is configured.  If the host has a
> 10.0.x.x network (and I suppose if we want to be thorough, a 10.0.x.x
> route), then it punts to 172.16.x.x (and does the same check) and then
> tries a couple of 192.168.x.x networks.

I really dislike this kind of guesswork.  It makes it very hard to 
debug/reproduce problems, and means you're never really sure what qemu is 
going to do.  IMHO One of the really nice features of qemu is that it is host 
independent.

Paul