[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] How to run Android on arm64?

On 08/22/2016 06:55 AM, Julien Grall wrote:
> Hello,
> On 20/08/16 01:05, J. Eppler wrote:
>> On 08/19/2016 10:04 AM, Julien Grall wrote:
>>> On 18/08/16 17:55, J. Eppler wrote:
>>>> On 08/18/2016 07:04 AM, Julien Grall wrote:
>>>>> On 15/08/16 07:05, J. Eppler wrote:
>> I used the kernel config:
>> http://xenbits.xen.org/people/sstabellini/config-hikey and the source
>> mentioned in https://wiki.xen.org/wiki/HiKey to build the kernel (I will
>> call it stabellini kernel). I used the same kernel (stabellini kernel)
>> to run Android, since I did not had any success with the Android kernel
>> from the pre-build 96Boards Android image.
>> I think the stabellini kernel works only with the Linux init system and
>> not with Android's init stystem. Both init systems are very different
>> from each other.
>> I thinks the solution would be to insert some of the Android specific
>> things in stabellini's kernel config, but I have no idea which one.
> It would be easier if you get an Android specific config and add Xen
> options in it.
> The following options are recommended for Xen:
> Cheers,
Hello Julien,

thanks for the hint that helped me a lot. I was able to build a working
android DomU kernel by enabling Xen support in an existing standard
configuration created with `make hikey_defconf`.

However, this did not resolve the init issue. While researching I
figured out that the `/init` directory is stored in the `ramdisk.img`.
Adding the `ramdisk.img` in my Android DomU config helped:

The result is a non crashing Android DomU, but the guest has a lot of
problems with `binder` transactions and filesystem. Those issues are not
related to Xen.

Best regards
  J. Eppler

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.