From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1JMi2Q-0005jj-7V
	for qemu-devel@nongnu.org; Wed, 06 Feb 2008 06:01:58 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1JMi2N-0005iy-Ko
	for qemu-devel@nongnu.org; Wed, 06 Feb 2008 06:01:57 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1JMi2M-0005iZ-8t
	for qemu-devel@nongnu.org; Wed, 06 Feb 2008 06:01:55 -0500
Received: from ug-out-1314.google.com ([66.249.92.169])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <balrogg@gmail.com>) id 1JMi2L-0001YA-JQ
	for qemu-devel@nongnu.org; Wed, 06 Feb 2008 06:01:53 -0500
Received: by ug-out-1314.google.com with SMTP id m2so371014uge.4
	for <qemu-devel@nongnu.org>; Wed, 06 Feb 2008 03:01:52 -0800 (PST)
Message-ID: <fb249edb0802060301t999a6c1y65b94def49607734@mail.gmail.com>
Date: Wed, 6 Feb 2008 12:01:52 +0100
From: "andrzej zaborowski" <balrogg@gmail.com>
Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
In-Reply-To: <18345.36535.82205.721504@mariner.uk.xensource.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <jey79zvgld.fsf@sykes.suse.de>
	<20080205005142.GD4368@implementation>
	<fb249edb0802051209j4c9e63bepb253d0cfa58c0590@mail.gmail.com>
	<20080205162206.38J1B.215136.root@eastrmwml22.mgt.cox.net>
	<200802052129.26282.paul@codesourcery.com>
	<20080206014031.GA5042@shareable.org>
	<alpine.DEB.1.00.0802051103230.31169@dell.linuxdev.us.dell.com>
	<20080205124219.EBPKE.19922.root@eastrmwml27.mgt.cox.net>
	<414CDEB1-8E31-4FAF-BE6F-1625F7FA77A6@web.de>
	<18345.36535.82205.721504@mariner.uk.xensource.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
Cc: andreas.faerber@web.de, Asheesh Laroia <asheesh@creativecommons.org>

On 06/02/2008, Ian Jackson <Ian.Jackson@eu.citrix.com> wrote:
> andrzej zaborowski writes ("Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x"):
> > This rfc talks about organisations and networks that are real, not
> > about the network inside qemu which doesn't have connectivity with
> > another qemu network.
>
> Address clashes are still a problem even if the two networks don't
> exchange packets, if there is any system which needs to be on both
> networks.  And of course in the qemu case the host is on both
> networks.

Right, but this happens so rarely (and there are no obvious symptoms
when it happens) that it's okay for the user to set up non-user-net
networking or issue this one line grep command posted in the original
message. A more useful addition would perhaps be a simple warning from
qemu when the host is in a network containing 10.0.2.0/8.

Indeed when you google "10.0.2.2 ip" half of the hits relate to qemu/kvm/vbox.

Regards