From: "Jonathan Kalbfeld" <jonathan.kalbfeld@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
Date: Mon, 4 Feb 2008 16:44:39 -0800 [thread overview]
Message-ID: <db7b3ca90802041644nd41b373qf0c00f2090a3c48f@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0802041618420.19311@dell.linuxdev.us.dell.com>
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
You can always do what I do --- run openvpn between my QEMU sessions and set
up private networks that way ;)
On Feb 4, 2008 4:24 PM, Asheesh Laroia <asheesh@creativecommons.org> wrote:
> I'm running qemu (really, KVM) in a LAN that uses 10.0.2.x as the IP
> address block for workstations. So naturally when I booted a guest, it
> couldn't access machines inside the LAN.
>
> I tried the simplest thing that could possibly work:
>
> paulproteus@sf:~/dnlds/qemu/qemu $ replace 10.0.2 10.0.3 -- `find
> -type f | grep -v -i CVS `
>
> Booting that resulted in a virtual machine that, as I had hoped, used
> 10.0.3.15 and could therefore successfully talk to my 10.0.2.x IPs on the
> LAN. I've attached a 'cvs diff' against HEAD that results from the above
> command.
>
> Out of curiosity, are there plans to make the user-space networking stack
> IP range configurable at run-time rather than compile time? I'm not
> suggesting that this patch I attached become part of CVS HEAD necessarily;
> what I do hope is that this will inspire someone else on the list to make
> the handling of this more flexible, knowing now that it's fairly easy to
> do. (-:
>
> Even if not, this serves as a report to others that this trivial patch
> actually does what you'd hope/expect!
>
> -- Asheesh.
>
> --
> It took me fifteen years to discover that I had no talent for writing,
> but I couldn't give it up because by that time I was too famous.
> -- Robert Benchley
>
--
--
Jonathan Kalbfeld
ThoughtWave Technologies LLC
www.thoughtwave.com
+1 424 354 1814
[-- Attachment #2: Type: text/html, Size: 2123 bytes --]
next prev parent reply other threads:[~2008-02-05 0:44 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 [this message]
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
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=db7b3ca90802041644nd41b373qf0c00f2090a3c48f@mail.gmail.com \
--to=jonathan.kalbfeld@gmail.com \
--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).