| Summary: | Connection Properties shows the network disabled, for UNFS qemuarm target | ||
|---|---|---|---|
| Product: | [Runtime] General Runtime | Reporter: | venkata ramana g <venkatarg> |
| Component: | General Runtime | Assignee: | venkata ramana g <venkatarg> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, cristian.iorga, sanil.kumar, sauravkg |
| Version: | 1.5 | ||
| Target Milestone: | 1.5 M4 | ||
| Hardware: | x86 | ||
| OS: | arm | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
venkata ramana g
2013-06-03 15:35:05 UTC
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. |