# Arm64: unprivileged LXD blocks Kubernetes tests **URL:** \ **Category:** Multi CPU Architecture\ **Created:** [December 3, 2019, 9:38am UTC](https://travis-ci.community/t/arm64-unprivileged-lxd-blocks-kubernetes-tests/6272 "2019-12-03T09:38:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![cyb70289](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/cyb70289/32/3315_2.png) [@cyb70289](https://travis-ci.community/u/cyb70289)\ **Post date:** [December 3, 2019, 9:38am UTC](https://travis-ci.community/t/arm64-unprivileged-lxd-blocks-kubernetes-tests/6272/1 "2019-12-03T09:38:00Z")
I tried to run ceph-csi CI on Travis Arm64 node. It failed when deploying kubernetes due to it cannot access privileged file system. Manually test inside virtual machine or privileged LXD is successful. Error log: [https://travis-ci.org/cyb70289/ceph-csi/builds/614335300](https://travis-ci.org/cyb70289/ceph-csi/builds/614335300) Is it possible to run Arm64 tests inside Virtual Machines? Unprivileged LXD may block many CI jobs. I see some similar issues. - [Debugging docker run issue on arm64](https://travis-ci.community/t/debugging-docker-run-issue-on-arm64/5491) - [Open /proc/sys/vm/overcommit\_memory: permission denied](https://travis-ci.community/t/open-proc-sys-vm-overcommit-memory-permission-denied/5570) ---
**Author:** ![native-api](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/native-api/32/430_2.png) [@native-api](https://travis-ci.community/u/native-api)\ **Post date:** [October 20, 2020, 2:04am UTC](https://travis-ci.community/t/arm64-unprivileged-lxd-blocks-kubernetes-tests/6272/2 "2020-10-20T02:04:58Z")
> **[The Travis CI Blog: Announcing General Availability of Graviton2 CPU Support!](https://blog.travis-ci.com/2020-09-11-arm-on-aws)** > > Back in May, we announced the upcoming support of being able to build and test your projects using the newly released AWS Graviton2 processor. This was a huge announcement for us and continues th...