# MLAT on VirtualBox Success **URL:** \ **Category:** ADS-B Flight Tracking\ **Created:** [June 4, 2021, 6:36pm UTC](https://discussions.flightaware.com/t/mlat-on-virtualbox-success/77331 "2021-06-04T18:36:52Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![hakubo](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/hakubo/32/92462_2.png) [@hakubo](https://discussions.flightaware.com/u/hakubo)\ **Post date:** [June 4, 2021, 6:36pm UTC](https://discussions.flightaware.com/t/mlat-on-virtualbox-success/77331/1 "2021-06-04T18:36:52Z")
I’m new to this, but I ran into the issue of MLAT not working on a Ubuntu 20 VirtualBox VM running as a guest to Ubuntu 16 with Virtual Box 6.0.24. Reading around I found a few people talking about it sometimes being a USB passthrough related timing issue, which wasn’t the case for me. My `/var/log/piaware.log` showed the following `Server status: not synchronized with any nearby receivers`, rather than the `Server status: clock unstable`. The FA Status page showed `Multilateration (MLAT): Supported / Enabled`, I had a green MLAT indicator, and my local dashboard showed MLAT as green. I ended up changing the following VM settings: Changed the system chipset to ICH9 Unchecked the Hardware Clock in UTC Time box (probably doesn’t matter) Set the USB controller to 3.0 (xHCI) I now have FA reporting `Multilateration (MLAT): Supported / Enabled (synchronized with 186 nearby receivers)` and the following in my logs: ```nohighlight Jun 4 10:42:02 flightaware piaware[957]: mlat-client(1072): Server status: synchronized with 190 nearby receivers Jun 4 10:42:02 flightaware piaware[957]: mlat-client(1072): Receiver: 250.2 msg/s received 105.0 msg/s processed (42%) Jun 4 10:42:02 flightaware piaware[957]: mlat-client(1072): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server Jun 4 10:42:02 flightaware piaware[957]: mlat-client(1072): Aircraft: 22 of 32 Mode S, 37 of 47 ADS-B used Jun 4 10:57:03 flightaware piaware[957]: mlat-client(1072): Receiver status: connected Jun 4 10:57:03 flightaware piaware[957]: mlat-client(1072): Server status: synchronized with 188 nearby receivers Jun 4 10:57:03 flightaware piaware[957]: mlat-client(1072): Receiver: 253.4 msg/s received 103.0 msg/s processed (41%) Jun 4 10:57:03 flightaware piaware[957]: mlat-client(1072): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server Jun 4 10:57:03 flightaware piaware[957]: mlat-client(1072): Results: 5.3 positions/minute Jun 4 10:57:03 flightaware piaware[957]: mlat-client(1072): Aircraft: 15 of 23 Mode S, 29 of 41 ADS-B used Jun 4 11:12:03 flightaware piaware[957]: mlat-client(1072): Receiver status: connected Jun 4 11:12:03 flightaware piaware[957]: mlat-client(1072): Server status: synchronized with 193 nearby receivers Jun 4 11:12:03 flightaware piaware[957]: mlat-client(1072): Receiver: 320.7 msg/s received 108.4 msg/s processed (34%) Jun 4 11:12:03 flightaware piaware[957]: mlat-client(1072): Server: 0.0 kB/s from server 0.0kB/s TCP to server 1.1kB/s UDP to server Jun 4 11:12:03 flightaware piaware[957]: mlat-client(1072): Results: 7.4 positions/minute Jun 4 11:12:03 flightaware piaware[957]: mlat-client(1072): Aircraft: 26 of 34 Mode S, 33 of 51 ADS-B used ``` So far so good about 10 hours in, I’m seeing MLAT planes and positions reported in FA. [ADSBX.org](http://ADSBX.org) has a handy MLAT debugger page that is also showing green for me ([Feeder (Region) MLAT - ADSBExchange](https://adsbx.org/sync/feeder.html?1B&hakubo)) Anyway, just wanted to share since I hadn’t been able to find anyone reporting success under VirtualBox. ---
**Author:** ![Jojogunne](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jojogunne/32/113056_2.png) [@Jojogunne](https://discussions.flightaware.com/u/Jojogunne)\ **Post date:** [April 8, 2022, 10:36pm UTC](https://discussions.flightaware.com/t/mlat-on-virtualbox-success/77331/2 "2022-04-08T22:36:09Z")
Just wanted to say thank you for this advice. I was having the same problem exactly. I knew I should be seeing MLAT peers, but wasn’t getting any. Used your settings and now it’s working as I would have expected. All the best. ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/system/32/38558_2.png) [@system](https://discussions.flightaware.com/u/system)\ **Post date:** [April 8, 2023, 10:36pm UTC](https://discussions.flightaware.com/t/mlat-on-virtualbox-success/77331/3 "2023-04-08T22:36:34Z")
Closed on April 8, 2023, 10:36pm UTC This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.