Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Christoffer Dall <cdall@linaro.org>, Roman Livshits <romanliv@gmail.com>
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: Android on virt device
Date: Thu, 2 Mar 2017 21:08:53 +0800	[thread overview]
Message-ID: <58B81965.6070402@huawei.com> (raw)
In-Reply-To: <20170302130442.GL1409@cbox>



On 2017/3/2 21:04, Christoffer Dall wrote:
> On Sun, Feb 26, 2017 at 12:12:35PM +0200, Roman Livshits wrote:
>> Hi
>>
>> I am trying to run Android on qemu virt machine.
>> I want to use virt as this was used by the op-tee for implementing
>> TEE for ARM TrustZone, see
>> https://github.com/OP-TEE/build#op-tee-buildgit, so hope that
>> running Android on virt would be easier comparing to putting op-tee
>> to ranchu, used by Android emulator
>> (http://www.linaro.org/blog/core-dump/running-64bit-android-l-qemu/).
>>
>> Is there any advice how to do this?
>>
> 
> You'd need an Android guest kernel that runs on the virt board and you
> may also need some userspace changes, because I believe the initial user
> deamons in Android loads libraries and hardware management layers based
> on the machine name (e..g Ranchu).
> 
> The biggest challenge, however, is probably going to get the number of
> devices needed to get Android booting properly so that you can interact
> with it working on the virt board.  For example, I'm not sure how you
> plan on dealing with the framebuffer/graphics.
> 
> Personally, for a quick solution, I would probably go the other route
> and first try to make Android run under KVM using the Ranchu device
> without any secure component.  Then I would look at bringing together
> the work in whichever of the two platforms you prefer.
> 
> The Ranchu platform should be relatively similar to the virt platform,
> so I wouldn't expect too much work in getting OP-TEE compiled and
> running with Ranchu.
> 
Maybe another way is porting the goldfish framebuffer to virt machine.

Thanks,
-- 
Shannon

      reply	other threads:[~2017-03-02 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 10:12 Android on virt device Roman Livshits
2017-03-02 13:04 ` Christoffer Dall
2017-03-02 13:08   ` Shannon Zhao [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=58B81965.6070402@huawei.com \
    --to=zhaoshenglong@huawei.com \
    --cc=cdall@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=romanliv@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox