[GSoC 2026] Android Development in Qubes VM

49 views
Skip to first unread message

Qasim ahmad

unread,
Mar 18, 2026, 6:27:09 AMMar 18
to qubes-devel

My name is Qasim. I’m a student at UBC, and I’m interested in the “Android development in Qubes VM” project for GSoC 2026.

I’ve been reading through the discussions around Android support and the current reliance on QEMU-emulated ARM images. The performance limitations and the move toward hardware-assisted virtualization (HVM) make a lot of sense.

I already run the OS as my daily driver, and I’m comfortable with Linux, Bash/Python scripting and virtualization concepts (QEMU/KVM, isolation, passthrough). I also have experience with C++ systems work, so I’m comfortable digging into lower-level debugging when needed.

I’m currently setting up a local environment to experiment with Android tooling, and had a couple quick questions:

  • Is there a preferred direction for hardware-accelerated Android (e.g., KVM-backed images vs adapting existing emulator flows)?

  • For inter-qube communication (ADB/debugging), are there existing Qubes patterns to build on?

  • Also, who would be the best person to coordinate with regarding mentorship for this project?

Thanks for your time


Regards,

Qasim

Message has been deleted

Marek Marczykowski-Górecki

unread,
Mar 19, 2026, 11:30:59 AM (13 days ago) Mar 19
to Qasim ahmad, qubes-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Wed, Mar 18, 2026 at 01:44:16AM -0700, Qasim ahmad wrote:
> My name is Qasim Khawaja. I’m a student at UBC, and I’m interested in the *“Android
> development in Qubes VM”* project for GSoC 2026.

Hello!


> I’ve been reading through the discussions around Android support and the
> current reliance on QEMU-emulated ARM images. The performance limitations
> and the move toward hardware-assisted virtualization (HVM) make a lot of
> sense.
>
> I already run Qubes OS as my daily driver, and I’m comfortable with Linux,
> Bash/Python scripting and virtualization concepts (QEMU/KVM, isolation,
> passthrough). I also have experience with C++ systems work, so I’m
> comfortable digging into lower-level debugging when needed.
>
> I’m currently setting up a local environment to experiment with Android
> tooling, and had a couple quick questions:
>
> -
>
> Is there a preferred direction for hardware-accelerated Android (e.g.,
> KVM-backed images vs adapting existing emulator flows)?

Currently Xen doesn't (in practice) support nested virtualization, so
you can't run KVM inside Qubes OS. This limits available options to:
1. Run plain QEMU (without KVM) in a qube - slow
2. Run Android VM as a separate qube, and add necessary integration.

For the second point, this would need to be x86 build of Android, not
ARM (there are several projects doing this). And "necessary integration"
would include stuff like:
- - ensuring proper drivers are available in Android and/or adjusting
hardware emulated by QEMU for Android to be happy
- - possibly network configuration in Android

> -
>
> For inter-qube communication (ADB/debugging), are there existing Qubes
> patterns to build on.

Theoretically, ADB over network just work out of the box. If something
like serial console would be needed, we used to have instruction how to
do that for Windows, it was quite hacky:
https://github.com/QubesOS/qubes-doc/blob/72052be4d5884e912152403ec6d15ca78bf0b1bf/developer/debugging/windows-debugging.md

> And also, who would be the best person to coordinate with regarding
> mentorship for this project?

I guess it would be me :)

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmm8FqwACgkQ24/THMrX
1ywQZwgAlTUinNremgVhwRMacP86aP54Cc8tZQOWDIhwtU06cbAH9kI77wm3/TZX
twD+0pAlri+dDqp8yx5tI8P7X0jpogEl0pe6i2TR/QY61gIGmO97ls+ezGPDVlTf
WnmLfZvt4tw/+Oip9D3N6hUTW/cvOxBM2olB/arP4s5NaimaoQfngs1mJbWvuCyX
j/siWm37JoGc/xE4qgnn4GWVIeDxVUsMUJwOjw18m4VbFgAvks/KrNzMlj1lTFuF
Mw1IHcagMg7zxuwJNoa/p7+tC06iP6NJF0wNehlhe3Amy3COc+1YUr+7mQU/HX8k
vDLK7p1EWpy564MvTdfOKSUUCApa5g==
=oSyx
-----END PGP SIGNATURE-----
Message has been deleted

Qasim ahmad

unread,
Mar 24, 2026, 1:48:40 AM (9 days ago) Mar 24
to qubes-devel
Hi Marek, thank you so much for your response. 
I have started working on replicating the environment and understanding the Qubes codebase (I opened PR#791 on qubes-core-admin).
I prepared an initial draft of the GSoC proposal and I was wondering what would be the best way to send it you to have a look? Should I upload it here as PDF or a google doc link?
Thank you so much and I hope to hear from you soon.
Regards,
Qasim

Marek Marczykowski-Górecki

unread,
Mar 24, 2026, 9:00:17 AM (8 days ago) Mar 24
to Qasim ahmad, qubes-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Mon, Mar 23, 2026 at 10:48:40PM -0700, Qasim ahmad wrote:
> Hi Marek, thank you so much for your response.
> I have started working on replicating the environment and understanding the
> Qubes codebase (I opened PR#791 on qubes-core-admin).
> I prepared an initial draft of the GSoC proposal and I was wondering what
> would be the best way to send it you to have a look? Should I upload it
> here as PDF or a google doc link?

PDF or even copy&paste into an email would be ok.
> --
> You received this message because you are subscribed to the Google Groups "qubes-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/qubes-devel/e9e3ade9-2e53-42a5-833b-2b2e571cd643n%40googlegroups.com.


- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmnCitcACgkQ24/THMrX
1yypbQf9Fm89KZMgsbelxkAbKSoh3zeyfL0rQNrrHo+lA7q74Q+wKl1LVhMhPcD5
Kkd4x0Wwp9zBZnTbVkOl/jkqL0x1QdA6Qs0Qwn3vt30HQk48qQNDmPOztXxF3PB+
ahXqbHBCT5TMgsj/9Ge4NKqywbSaRK/407d+yAspVZclYtsp17IGsZPzC4GDD5UH
h0OLEt0riDJb3KdJU/1DUxeyI+GmV4jAR38RbInGbqtor5eGySkNxqsbTtEjQIPY
UU4lONMPrYcQMnSC7rro+p35cOvqVajUj+zzN4vRkvVKZJZrjaZKdAEE4i7Q8vvl
ubimITo9+Un9HQeDP5LeZXieuBjY8Q==
=SY5o
-----END PGP SIGNATURE-----

Qasim ahmad

unread,
Mar 25, 2026, 2:49:29 AM (8 days ago) Mar 25
to qubes-devel
Hi thank you so much for your response, I sent it to your email.
Regards,
Qasim Khawaja

Qasim ahmad

unread,
Mar 31, 2026, 2:28:15 AM (yesterday) Mar 31
to qubes-devel
Hi Marek, while I was reading this forum https://forum.qubes-os.org/t/android-vm-with-qubes-os/31240/3, I am able to replicate Android-x86 running inside a QEMU-based VM in Qubes and started looking into moving it to a native Xen HVM. One thing I’m a bit confused about is how device support is expected to translate, I know that in the QEMU setup Android relies on virtio devices, but I’m not sure what the equivalent setup would look like under Xen in Qubes.
Would you have any suggestions?
Thanks

Marek Marczykowski-Górecki

unread,
Mar 31, 2026, 6:09:10 PM (22 hours ago) Mar 31
to Qasim ahmad, qubes-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


On Mon, Mar 30, 2026 at 11:28:14PM -0700, Qasim ahmad wrote:
> Hi Marek, while I was reading this
> forum https://forum.qubes-os.org/t/android-vm-with-qubes-os/31240/3, I am
> able to replicate Android-x86 running inside a QEMU-based VM in Qubes and
> started looking into moving it to a native Xen HVM. One thing I’m a bit
> confused about is how device support is expected to translate, I know that
> in the QEMU setup Android relies on virtio devices, but I’m not sure what
> the equivalent setup would look like under Xen in Qubes.
> Would you have any suggestions?

HVM under qubes also uses QEMU (just isolated in a stubdomain), so
virtio may still be an option for devices. Alternatively fully emulated
devices could be used - just need to find appropriate models that are
supported by android.
> To view this discussion visit https://groups.google.com/d/msgid/qubes-devel/5911aa28-b798-4568-ba42-b8913b131e66n%40googlegroups.com.


-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEhrpukzGPukRmQqkK24/THMrX1ywFAmnMRgAACgkQ24/THMrX
1yzdxAf/To8SiZtu9Wsb+4PBMMRkfDtqcS54wrEEi5NXvZD79xv9DW622mL0dh2j
zXwkqxliBQwMALjdTiis+7OIh8C7lY0/pBIwGUqQxPA8wxoiqkTMYEeJ6JDqTCyt
o9u+LTV8aBNStbb4KuS5/22c9ThC3d3rGVxEBvtr3zm8zMJdvNLhLTCCOMk4W3Lt
pVIDx8P3UqjxuSVFq5dZsaXocCgHosi08kcAHDmPRNnehMadNVTgyvNf/BRjJTa/
xXaTNA2ybnYCXbyABV6IwaqZPN9+CvI862YxjeeFHHaqR1RxFGPAFfzJ1aKshU+z
NsEfpFxl/A+wT9rX5Df2rkYrnShmjQ==
=bkEw
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages