[OE-core] [PATCH V3 2/2] connman-conf: configures connman in qemu machines

[Iorga, Cristian]

Hello Enrico, see my answers below.

Regards,
Cristian

-----Original Message-----
From: Enrico Scholz [mailto:enrico.scholz at sigma-chemnitz.de] 
Sent: Friday, January 11, 2013 2:23 PM
To: openembedded-core at lists.openembedded.org
Cc: Cristian Iorga
Subject: Re: [PATCH V3 2/2] connman-conf: configures connman in qemu machines



Cristian Iorga <cristian.iorga-ral2JQCrhuEAvxtiuMwx3w at public.gmane.org>
writes:

> For qemu machines, connman should not configure virtual wired interfaces.

This is not a qemu-only problem but affects all platforms with nfs rootfs, isn't it?
	In this particular case, it's only related to qemu in the network environment presented to a virtual machine.
	There is a separate patch for the $nfsroot issue.

Setup whether to disable configuration of interface should be done dynamically and based on e.g. whether rootfs is on nfs and/or if kernel cmdline contains 'ip=...'.
	In my opinion, that's debatable. Qemu images for sure won't have a DHCP to send request too (as the setup is done now); as such, the build system can decide in advance to blacklist ethn to connman.
	To me, the $nfsroot fix is OK. It is done dynamically done, and on need by need base.



> Wired interfaces (eth0) are assigned static IP addresses by the 
> virtual machine manager (qemu). This packages places the eth0 
> interface in a list of blacklisted interfaces, forbiding connman 
> administering wired interfaces for qemu machines.

Unfortunatly, this breaks DNS in the machine because DNS server information are not retrieved from DHCP anymore :(
	In which machine? qemu*? Is there a DHCP server to work with? That's the main problem that I am seeing, that there is no DHCP server, and, in the end, connman will assign a Zeroconf IP address to eth0.
	As far as I know, there will be no DNS server set if Zeroconf is used.



Enrico