Re: runqemu + dhcp server

[Patrick Ohly <patrick.ohly@intel.com>]

Adrian Freihofer <adrian.freihofer@...> writes:
> Personally I would prefer a slightly different implementation.
> I consider the 192.168.7.2 network interface as development, debugging
> and testing interface which should just work.

Agreed, and it doesn't work at the moment when the image has an Ethernet
configuration mechanism that wasn't adapted to use the ip kernel parameter. 
What you are proposing goes beyond just fixing that. I don't have any strong
opinion about the right way forward.

> By the way, where does your solution make use of the DHCP server?

When Connman starts up, it finds eth0 and obtains an IP address for it via
DHCP. Without the DHCP server, the guest ends up without an IP address. I
have not checked if the ip parameter was ever used.

Note that this is what the default Tizen Connman config does, not what Poky
would do when building and installing Connman. The whole point was the
ability to use production images without special tweaks. 

> The 
> eth0 IP configuration is assigned by kernel boot parameters in
> runqemu-internal. If this configuration gets changed later on the NFS 
> rootfs will break...

I haven't tried NFS rootfs. My hope is that it would still work because the
ip parameter and the DHCP server assign the same IP address and thus nothing
changes inside the guest when switching from one to the other.