Thank you for sharing the details. I believe you have also seen the below log
when the emulator starts.
init: could not import file '/init.carrier.rc' from '/init.rc'
init: cannot open '/initlogo.rle'
init: cannot find '/system/bin/sysinit', disabling 'sysinit'
init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
init: cannot find '/system/bin/qemu-props', disabling 'qemu-props'
It means that android init has started, what it needs is the bin files in
/system/bin. I don't know why the system.img is not working. I tried argument
like " -system out/target/product/generic/system.img " for emulator, and got
no luck. Have you fixed this yet?
To: leon lee <llrraa@xxxxxx>
From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
Date: Fri, 4 Oct 2013 09:23:29 +0100
Cc: ubuntu-phone <ubuntu-phone@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <tencent_46ae2435640f30cc182b7...@qq.com>
Sender: dmitrij.ledkov@xxxxxxxxxxxx
On 4 October 2013 08:45, leon lee <llrraa@xxxxxx> wrote: > I manage to do the
same as you by running run-emulator.sh. But I'm not > familiar with lxc
container, so can you please share some details on how it > works with the
android part. > Recent devices are using "flipped model" that is ubuntu is
booted from the initramfs, and then lxc container is started to boot the
minimal android system we need to bring up the rest of the hardware support.
The details are sparse and it's easiest to look into existing devices
grouper/mako/maguro/manta which do use it. I had a chat with stephane, I think
I'll be able to use exactly the same boot process as system images. I'll keep
this mailing list posted on my progress. Regards, Dmitrijs.
.--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp
