Build: http://autobuilder.yoctoproject.org/pub/nightly/20130528-2/ Host Machine: Open Suse12.3 Platform : Qemuarm Problem: When Qemuarm target is brought up using UNFS, connection properties in UI shows network disabled. Though IP is correctly assigned to target and ssh to target is success. > runqemu-extract-sdk core-image-sato-qemuarm.rootfs.tar.bz2 rootfs > runqemu nfs zImage-qemuarm.bin rootfs Connection properties in GUI shows network disabled. ssh qemuarm target is success. ifconfig on target shows ip correctly. When Qemu is brought up using non-UNFS, using core-image-sato-qemuarm.rootfs.ext3 Connection properties works correctly with out any problem.
I'm pretty sure this is expected. Because the network interface cannot be brought down or reconfigured in any way after boot because the root filesystem relies upon it, connman cannot have anything to do with managing the interface.
Investigation started.
Please provide a test case.
During connman startup (systemV init script) if a NFS root is defined (such is the case when a qemu image is started using NFS) then all eth* interfaces are set to be ignored by connman, so that connman will not disconnect the virtual machine from the networks and render it unusable.