From: Paul Brook <paul@codesourcery.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 03:34:24 +0000 [thread overview]
Message-ID: <200802060334.26701.paul@codesourcery.com> (raw)
In-Reply-To: <20080206014031.GA5042@shareable.org>
On Wednesday 06 February 2008, Jamie Lokier wrote:
> Paul Brook wrote:
> > > > 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.
>
> If it _doesn't_ guess, i.e. uses the fixed default of 10.0.2.x (or any
> other), then it's _not_ host independent.
Well, obviously anything that involves talking to the host or the outside
world is never going to completely host independent. Your case will also
break if you run it on a machine with no internet connection.
The environment inside qemu is consistent.
If you have qemu automagically guess things then the gust OS also has to be
capable of coping with things changing underneath it.
Paul
next prev parent reply other threads:[~2008-02-06 3:34 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 [this message]
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=200802060334.26701.paul@codesourcery.com \
--to=paul@codesourcery.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).