Android as domU (xen / hikey)

Products Support HiKey
#1

Hello,

I’m trying to get android running as domU on hikey.
I followed the instructions in xen-wiki and I successfully get xen running with centos7 as dom0.
With android, I was able to boot the kernel fine and it mounts /system and /data and /cache but the problem that just before the boot animation, I get an infinite loop like this:

hikey:/ $ [ 5.342234] healthd: No battery devices found
[ 6.955623] init: Service ‘surfaceflinger’ (pid 1350) killed by signal 6
[ 6.955691] init: Service ‘surfaceflinger’ (pid 1350) killing any children in
process group
[ 6.955781] init: Service ‘zygote’ is being killed…
[ 6.981406] init: Service ‘zygote’ (pid 1358) killed by signal 9
[ 6.981469] init: Service ‘zygote’ (pid 1358) killing any children in process
group
[ 6.981757] init: write_file: Unable to open ‘/sys/android_power/request_stat
e’: No such file or directory
[ 6.981900] init: write_file: Unable to write to ‘/sys/power/state’: Invalid
argument
[ 6.981969] init: Service ‘media’ is being killed…
[ 6.982086] init: Service ‘netd’ is being killed…
[ 6.994535] init: Service ‘netd’ (pid 1364) killed by signal 9
[ 6.994587] init: Service ‘netd’ (pid 1364) killing any children in process g
roup
[ 6.996554] init: Untracked pid 1431 killed by signal 9
[ 7.003104] init: Service ‘media’ (pid 1363) killed by signal 9
[ 7.003155] init: Service ‘media’ (pid 1363) killing any children in process
[ 6.982086] init: Service ‘netd’ is being killed…
[ 6.994535] init: Service ‘netd’ (pid 1364) killed by signal 9
[ 6.994587] init: Service ‘netd’ (pid 1364) killing any children in process g
roup
[ 6.996554] init: Untracked pid 1431 killed by signal 9
[ 7.003104] init: Service ‘media’ (pid 1363) killed by signal 9
[ 7.003155] init: Service ‘media’ (pid 1363) killing any children in process
group
[ 10.005504] init: Starting service ‘zygote’…
[ 10.006718] init: Starting service ‘media’…
[ 10.007802] init: Starting service ‘netd’…
[ 10.013036] init: Starting service ‘surfaceflinger’…
[ 11.706007] init: Service ‘surfaceflinger’ (pid 1441) killed by signal 6
[ 11.706067] init: Service ‘surfaceflinger’ (pid 1441) killing any children in
process group

Any idea? any suggestions ??

Thanks

#2

Hi,

I don’t have the answer for your question, but could you please tell me what exact files do you use for your Android guest? Which guest kernel, rootfs, etc. I try to accomplish the same thing except with KVM.

Thanks

#3
init: Service ‘surfaceflinger’ (pid 1441) killed by signal 6 [ 11.706067] init: Service ‘surfaceflinger’ (pid 1441) killing any children in process group

signal 6 means SIGABRT, in this case I suspect SurfaceFlinger (which is required to put up the boot animation) has called abort() because it cannot set up the GFX systems within Xen.

#4

It looks to me like you have only grabbed the kernel logs. Do the android logs (which I’ve always found by running “logcat”) offer any clues about what’s happening inside SurfaceFlinger?