Latest GCP kernel has Android related config options disabled

Bug #1937987 reported by Simon Fels
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-gcp (Ubuntu)
New
Undecided
Unassigned

Bug Description

In LP:1849493 we enabled support for CONFIG_ANDROID_* on the gcp kernels to support Anbox Cloud. However checking on the latest rolling kernel on GCP (5.8.0-1038-gcp #40~20.04.1-Ubuntu ) gives

morphis@anbox0:~$ cat /boot/config-5.8.0-1038-gcp | grep CONFIG_AND
# CONFIG_ANDROID is not set

This is a regression and already affects customers of Anbox Cloud which intend to deploy on GCP and currently fail as the binder and ashmem kernel modules are missing. From the git history I wasn't able to figure out where the options got dropped.

The following options are what we need

CONFIG_ANDROID=y
CONFIG_ANDROID_BINDER_IPC=m
CONFIG_ANDROID_BINDERFS=m
CONFIG_ANDROID_BINDER_DEVICES=""
# CONFIG_ANDROID_BINDER_IPC_SELFTEST is not set
CONFIG_ASHMEM=m

These options should be set by default in all our cloud kernels, regardless which Ubuntu version.

Can we get some regression testing in place for this too?

Thanks!

Tags: anbox-cloud
Simon Fels (morphis)
tags: added: anbox-cloud
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.