From: Eddie Kohler <kohler@cs.ucla.edu>
To: qemu-devel@nongnu.org
Cc: andreas.faerber@web.de
Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
Date: Tue, 05 Feb 2008 08:16:05 -0800 [thread overview]
Message-ID: <47A88BC5.3020907@cs.ucla.edu> (raw)
In-Reply-To: <20080205.084836.74710742.imp@bsdimp.com>
Warner Losh wrote:
> From: Andreas Färber <andreas.faerber@web.de>
> Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
> Date: Tue, 5 Feb 2008 13:58:28 +0100
>
>> Am 05.02.2008 um 12:30 schrieb Ian Jackson:
>>
>>> I don't believe that 10.0.2.0/24 was chosen randomly :-). It would be
>>> better for qemu's default range to be a randomly chosen one.
>> Please don't randomly choose a default subnet; knowing that QEMU uses
>> 10.0.2.x allows to adapt to this. If however QEMU starts randomly
>> assigning addresses we will also get random conflicts.
>>
>> Please stick with a default like the current and simply make it
>> statically configurable.
>
> I think that the suggestion is that qemu picks, one time, a new
> default. This new default would be selected at random, and would be
> the same on all new versions of qemu.
>
> I don't think that the suggestion is to pick a random address every
> time qemu starts.
I already have some scripts that depend on the 10.0.2.x default -- probably
others do too. Would changing to a different subnet by default really make
that much difference? 10.0.2.x is, after all, a possible "random" choice :)
Eddie
next prev parent reply other threads:[~2008-02-05 16:16 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 [this message]
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
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=47A88BC5.3020907@cs.ucla.edu \
--to=kohler@cs.ucla.edu \
--cc=andreas.faerber@web.de \
--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).