# Source packages?

**URL:** <https://discussions.flightaware.com/t/source-packages/69802>\
**Category:** ADS-B Flight Tracking\
**Created:** [October 7, 2020, 11:34am UTC](https://discussions.flightaware.com/t/source-packages/69802 "2020-10-07T11:34:11Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![obj](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/obj/32/118984_2.png) [@obj](https://discussions.flightaware.com/u/obj)\
**Post date:** [October 23, 2020, 12:11am UTC](https://discussions.flightaware.com/t/source-packages/69802/32 "2020-10-23T00:11:58Z")

</div>

> [@zenonp](#):
>
> So this means we can’t run ARM binaries on an x86 VM host, unless this problem is overcome.

Well… you wouldn’t want to do that anyway (at least for dump1090/dump978), you would need a beefy CPU to emulate ARM at the speed needed to keep up with realtime.

> [@zenonp](#):
>
> How long ago was it you did those tests?

Year ago maybe? It’ll be on these forums somewhere.

> [@zenonp](#):
>
> Did you test any other virtualisation environments, say KVM/qemu or VMware?

Wasn’t my test or VM, I just diagnosed the problem from the mlat server side.

edit: previously:

- [Required packages for running piaware, and more about mlats](https://discussions.flightaware.com/t/required-packages-for-running-piaware-and-more-about-mlats/46613)
- ["Server status: clock unstable" - #4 by obj](https://discussions.flightaware.com/t/server-status-clock-unstable/19482/4)

---

_[View the full topic](https://discussions.flightaware.com/t/source-packages/69802)._