On Tue, 5 Feb 2008, Jernej Simončič wrote:
On Tuesday, February 5, 2008, 22:34:04, Asheesh Laroia wrote:
I agree with this - guesswork and invisible options can be confusing.
That's why I suggest what I think is the simplest solution: Just let
this be overridable on the command line.
On Tue, 5 Feb 2008, 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 b
On Tue, 5 Feb 2008, Ben Taylor wrote:
It seems to me that there is a corner case where the local host has a
10.0.2.x or 10.0.x.x address which would cause a qemu guest problems
that has a 10.0.2.15 address (for -net user only).
That's right - that's the issue that I faced.
I think the defau
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:
[EMAIL PROTECTED]:~/dnlds/qemu/qemu $ replace 10.0.
