From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Cc: andreas.faerber@web.de, Asheesh Laroia <asheesh@creativecommons.org>
Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
Date: Wed, 6 Feb 2008 12:01:52 +0100 [thread overview]
Message-ID: <fb249edb0802060301t999a6c1y65b94def49607734@mail.gmail.com> (raw)
In-Reply-To: <18345.36535.82205.721504@mariner.uk.xensource.com>
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
next prev parent reply other threads:[~2008-02-06 11:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 0:24 [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x Asheesh Laroia
2008-02-05 0:44 ` Jonathan Kalbfeld
2008-02-05 0:51 ` Samuel Thibault
2008-02-05 10:32 ` Andreas Schwab
2008-02-05 10:44 ` Samuel Thibault
2008-02-05 11:30 ` Ian Jackson
2008-02-05 12:58 ` Andreas Färber
2008-02-05 15:48 ` Warner Losh
2008-02-05 16:16 ` Eddie Kohler
2008-02-05 17:42 ` Ben Taylor
2008-02-05 19:06 ` Asheesh Laroia
2008-02-05 21:22 ` Ben Taylor
2008-02-05 21:29 ` Paul Brook
2008-02-05 21:34 ` Asheesh Laroia
2008-02-05 22:12 ` Jernej Simončič
2008-02-05 22:24 ` Asheesh Laroia
2008-02-06 1:40 ` Jamie Lokier
2008-02-06 3:34 ` Paul Brook
2008-02-06 10:40 ` Ian Jackson
2008-02-06 11:01 ` andrzej zaborowski [this message]
2008-02-06 16:36 ` Ian Jackson
2008-02-06 12:39 ` Gerd Hoffmann
2008-02-05 20:09 ` andrzej zaborowski
2008-02-05 20:31 ` Blue Swirl
2008-02-05 21:46 ` Flavio Visentin
2008-02-05 0:56 ` Johannes Schindelin
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=fb249edb0802060301t999a6c1y65b94def49607734@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=andreas.faerber@web.de \
--cc=asheesh@creativecommons.org \
--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).