[GitHub] [cloudstack] rhtyd opened a new pull request #3644: [WIP] IoT support: allow cloudstack-agent on Raspberry Pi 3/4 (arm64) to use kvm acceleration

[GitBox <gi...@apache.org>]

rhtyd opened a new pull request #3644: [WIP] IoT support: allow cloudstack-agent on Raspberry Pi 3/4 (arm64) to use kvm acceleration
URL: https://github.com/apache/cloudstack/pull/3644
 
 
   KVM is supported on arm64 Linux (https://www.linux-kvm.org/page/Processor_support#ARM:). For a small (IoT) platform such as the new Raspberry Pi 4 that uses armv8 processor (cortex-a72) it's possible to run Linux host with `/dev/kvm` accleration.
   
   This PR is from a fun weekend project where:
   - I set up a Raspberry Pi 4 - 4GB RAM model with 4 CPU cores @ 1.5Ghz, 128GB SD samsung evo plus card
   - Installed Ubuntu 19.10 raspi3 base image: http://cdimage.ubuntu.com/releases/19.10/release/ubuntu-19.10-preinstalled-server-arm64+raspi3.img.xz
   - Build a custom Linux 5.3 kernel with KVM enabled, deb here: http://dl.rohityadav.cloud/cloudstack-rpi/kernel-19.10/ and install the linux-image and linux-module
   - Then install/setup CloudStack on it (fix some issues around jna, by manually installing newer libjna-java to /usr/share/cloudstack-agent/lib)
   - Since the host processor is not x86_64, I had to build a new arm64 (or aarch64) systemvmtemplate: http://dl.rohityadav.cloud/cloudstack-rpi/systemvmtemplate/
   
   I could finally get a 4.13 CloudStack + Adv zone/networking to run on it and deployed a KVM based Ubuntu 19.10 environment and NFS storage. Deployed a test vm with isolated network, VR works as expected. Console proxy works as well, for this tested against arm64 openstack Debian 9/10 templates.
   
   ## Types of changes
   <!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
   - [ ] Breaking change (fix or feature that would cause existing functionality to change)
   - [x] New feature (non-breaking change which adds functionality)
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [ ] Enhancement (improves an existing feature and functionality)
   - [ ] Cleanup (Code refactoring and cleanup, that may add test cases)
   
   ## Screenshots (if appropriate):
   
   ![Screenshot from 2019-10-18 16-55-23](https://user-images.githubusercontent.com/95203/67157162-0c3b8b80-f346-11e9-9e00-b1460b676477.png)
   ![Screenshot from 2019-10-18 17-20-49](https://user-images.githubusercontent.com/95203/67157163-0cd42200-f346-11e9-98ca-97e5a63a04a7.png)
   ![Screenshot from 2019-10-20 01-43-43](https://user-images.githubusercontent.com/95203/67157164-0d6cb880-f346-11e9-9cae-d7f94f410062.png)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services