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. VM images which run perfectly on many hosts will breaks on some hosts, which happen to use a conflicted subnet on their host interfaces. That's not host independence. Whereas if it does the auto-selection suggested (I don't regard "pick an address not used already by the host" as guesswork), then many VM images will run without change on more hosts. It makes sense to have a configuration option to statically set the subnet used by Qemu, of course. Auto-selection seems like it would be useful for some things - especially VM images which are shipped with "run Qemu with these options to use this image". -- Jamie
