Support Android hypervisors

Support Android hypervisors

[RR NN]

[-- Attachment #1: Type: text/plain, Size: 170 bytes --]

 Android Virtualization Framework (AVF) supports "KVM(pKVM)" also
Qualcomm's "Gunyah" and MediaTek's "GenieZone" as the hypervisor. Please
Add these hypervisors to QEMU.

[-- Attachment #2: Type: text/html, Size: 232 bytes --]

Support Android hypervisors

[RR NN]

[-- Attachment #1: Type: text/plain, Size: 169 bytes --]

Android Virtualization Framework (AVF) supports "KVM(pKVM)" also Qualcomm's
"Gunyah" and MediaTek's "GenieZone" as the hypervisor. Please Add these
hypervisors to QEMU.

[-- Attachment #2: Type: text/html, Size: 255 bytes --]

Re: Support Android hypervisors

[Trilok Soni]

On 2/21/2024 9:37 PM, RR NN wrote:
> Android Virtualization Framework (AVF) supports "KVM(pKVM)" also Qualcomm's
> "Gunyah" and MediaTek's "GenieZone" as the hypervisor. Please Add these
> hypervisors to QEMU.

I don't understand this comment. Do you want QEMU to work as VMM as well
for these Hypervisors? AVF works w/ CrosVM as VMM. 

Recently Vatsa had submitted RFC for supporting QEMU w/ Gunyah. You can check
that as an example. 

-- 
---Trilok Soni

Re: Support Android hypervisors

[Alex Bennée]

RR NN <rnn59437@gmail.com> writes:

> Android Virtualization Framework (AVF) supports "KVM(pKVM)"

Does the user-space API change for pKVM? As far as I'm aware the
userspace API is the same.

> also Qualcomm's "Gunyah"

Feel free to review:

  https://patchew.org/QEMU/20240109090039.1636383-1-quic._5Fsvaddagi@quicinc.com/

> and MediaTek's "GenieZone" as
> the hypervisor. Please Add these hypervisors to QEMU.

Generally the QEMU community hasn't the bandwidth to implement every
requested feature so we rely on those with an interest to step forward
and work on the code.

That said it doesn't look like the kernel side of UAPI is anywhere close
to getting merged:

  https://lore.kernel.org/lkml/20240129083302.26044-1-yi-de.wu@mediatek.com/

I should also note that proprietary hypervisors locked to specific SoC's
make it even more challenging for open source developers to work on it.
I for one wouldn't want to try and get a hypervisor working if I
couldn't see the code and get it up and running under QEMU's emulation.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro

Re: Support Android hypervisors

[RR NN]

[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]

🙏

RR reacted via Gmail
<https://www.google.com/gmail/about/?utm_source=gmail-in-product&utm_medium=et&utm_campaign=emojireactionemail#app>

On Thu, Feb 22, 2024, 14:09 Alex Bennée <alex.bennee@linaro.org> wrote:

> RR NN <rnn59437@gmail.com> writes:
>
> > Android Virtualization Framework (AVF) supports "KVM(pKVM)"
>
> Does the user-space API change for pKVM? As far as I'm aware the
> userspace API is the same.
>
> > also Qualcomm's "Gunyah"
>
> Feel free to review:
>
>
> https://patchew.org/QEMU/20240109090039.1636383-1-quic._5Fsvaddagi@quicinc.com/
>
> > and MediaTek's "GenieZone" as
> > the hypervisor. Please Add these hypervisors to QEMU.
>
> Generally the QEMU community hasn't the bandwidth to implement every
> requested feature so we rely on those with an interest to step forward
> and work on the code.
>
> That said it doesn't look like the kernel side of UAPI is anywhere close
> to getting merged:
>
>
> https://lore.kernel.org/lkml/20240129083302.26044-1-yi-de.wu@mediatek.com/
>
> I should also note that proprietary hypervisors locked to specific SoC's
> make it even more challenging for open source developers to work on it.
> I for one wouldn't want to try and get a hypervisor working if I
> couldn't see the code and get it up and running under QEMU's emulation.
>
> --
> Alex Bennée
> Virtualisation Tech Lead @ Linaro
>

[-- Attachment #2: Type: text/vnd.google.email-reaction+json, Size: 40 bytes --]

{
  "emoji": "🙏",
  "version": 1
}

[-- Attachment #3: Type: text/html, Size: 2318 bytes --]