I am also giving links of pastebin in case attachment are not available error_log - http://pastebin.com/e3p8nFtA logcat_container- http://pastebin.com/pxjN9305 logcat_host - http://pastebin.com/SJZ95THf lxc_debug_file- http://pastebin.com/rMdeA6N5 PivotrootInvalidArugment.patch -http://pastebin.com/RPYn21RU
On Tuesday, January 22, 2013 2:07:01 PM UTC+5:30, me sdkie wrote: > > Hi, > We(group of 4 members) are trying to run LXC <http://lxc.sourceforge.net/>on > Android platform. Things we have done till now, > > - Statically linked the LXC tools for ARM platform[1] > - Patch the goldfish 2.6.29 kernel to remove error of *"Invalid > argument"* thrown by *pivot_root* syscall > - Tested LXC binaries by creating busybox container on Emulator > running Android 4.1.1 > > Now creating rootfs for container > > - Copied the content of stock Android having /data and /system folders. > - Removed the mounting commands from init.rc of container > - To simplify problem we have striped down the host android to run > only uevent daemon and starting container directly using init.rc > > When we start the container, zygote restarts continuously, because of > which media and netd also restarts. > Error log: > > init: waitpid returned pid 10, status = 00000009 >> >> init: process 'zygote', pid 10 exited >> >> init: process 'zygote' killing any children in process group >> >> request_suspend_state: wakeup (3->0) at 24151891747 (2013-01-21 >>> 15:17:27.117129135 UTC) >> >> init: service 'media' is being killed >> >> init: starting 'media' >> >> init: service 'netd' is being killed >> >> init: starting 'netd' >> >> init: waitpid returned pid 6, status = 00000009 >> >> init: untracked pid 6 exited >> >> init: starting 'zygote' >> >> init: waitpid returned pid 12, status = 00000009 >> >> init: Created socket '/dev/socket/mdns' with mode '660', user '0', group >>> '1000' >> >> init: Created socket '/dev/socket/zygote' with mode '660', user '0', >>> group '1000' >> >> init: Created socket '/dev/socket/dnsproxyd' with mode '660', user '0', >>> group '3003' >> >> init: Created socket '/dev/socket/netd' with mode '660', user '0', group >>> '1000' >> >> init: waitpid returned pid 174, status = 00000009 >> >> > After comparing logcat output of container running on striped android and > full Android host using* vimdiff, *we realised that dalvikvm fails to set > capabilites: operation not permitted, and libc gives segmentation fault. > > I/dalvikvm: System server process 168 has been created >> >> E/dalvikvm: cannot set capabilities (7c13c20,7c13c20): Operation not >>> permitted >> >> E/dalvikvm: VM aborting >> >> F/libc : Fatal signal 11 (SIGSEGV) at 0xdeadd00d (code=1), thread 168 >>> (zygote) >> >> I/Zygote : Accepting command socket connections >> >> I/DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** >>> *** >> >> I/DEBUG : Build fingerprint: >>> 'Android/full/generic:4.1.1/JRO03R/eng.root.20121008.012639:eng/test-keys' >> >> I/DEBUG : pid: 168, tid: 168, name: UNKNOWN >>> zygote <<< >> >> I/DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadd00d >> >> > We have attached logcat output of both container and host. > @IIja herdt - Can you provide us with the patch which you have created for > nexus one container to study?[2] > Please share your experience so that we get the zygote working. > > [1] https://github.com/SDkie/LXC-for-ARM > [2] http://code.google.com/p/seek-for-android/wiki/AndroidContainer > -- > Mind Workers > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
