- VM based based Anbox instance does support a subset of VIRTIO, but not fully, but scalability is limited compared to container.
Scalability for VMs on Anbox Cloud is not necessarily limited but it has the additional overhead of running a virtualization layer (e.g. requires nested virtualization if not running bare metal which for example is not present on Arm currently available through public clouds).
To what extent does Anbox Cloud support emulation and continuous testing of Android systems for vehicles?
We for example have extensive support for the VHAL part, you can find more details at the following parts of our documentation
- https://documentation.ubuntu.com/anbox-cloud/explanation/aaos/
- https://documentation.ubuntu.com/anbox-cloud/howto/android/custom-vhal/
- https://documentation.ubuntu.com/anbox-cloud/howto/android/integrate-hidl/
- https://documentation.ubuntu.com/anbox-cloud/reference/api-reference/anbox-https-api/#vhal
You can also directly used the VHAL remotely through our UI or integrate it into your own UI implementations.
- Specifically, in the role of a developer up to which layer (application Layer, Service Layer, HAL, BSP layer) can we deploy our own implementation , test and emulate using Anbox Cloud ?
for example, an OEM request for an application demands us to have a new driver, which needs customized Hardware Abstraction Layer (HAL), and then required application need to be developed, how can Anbox Cloud facilitate this process?
At this point it is not possible to replace the vendor layer within Anbox Cloud. An exception is the VHAL implementation which can be externally provided, see the links from above for more details. The main reason for this is that our vendor layer is what provides the integration with our streaming solution and tight integration with for example data center GPUs (NVIDIA, AMD Intel).
If there are specifics needs for customized or new HAL interfaces, there is an option to place them as part of the ODM partition as long as they are built against the same VINTF version as the rest vendor layer. If there are specifics needs for other HAL interfaces, it would be best to have a conversation to understand the needs better.
You can provide your own Android system image to Anbox Cloud which is then placed on top of our vendor image for integration with the Anbox runtime. The system image is built from your sources as part of that process and is fully in your hands. A requirement for this is a commercial engagement with Canonical so we can provide the necessary service to enable support for your system image, transfer knowledge and train your team on how to maintain support going forward.
- What is the roadmap for supporting general Android features, such as Bluetooth and other currently unsupported functionalities, in Anbox Cloud? Are there any timelines or updates available for these features?
We are subject to feedback we receive from our users on what is most critical to add to our roadmap. We maintain a public roadmap and if you’re interested in particular features (e.g. Bluetooth) we’re more than happy to have a conversation on how we can best support your needs.