Depending on which network (usually from home) the VM was started on, it can be that the hostname `sandbox.kylo.io` gets resolved to an IP similar to `188.8.131.52`, and not the `10.0.2.15`, which is the one Ambari has registered the services. This means that Ambari can't start/monitor the services.
Fetch the IP adress that Ambari has registered for sandbox.kylo.io, or run `ip adress` -> get the non-looping IP (not 127.0.0.1)
update /etc/hosts -> add new line with `<ambari-IP/ non-loopback-IP> sandbox.kylo.io`
Run `service network restart`
Re-check Ambari. if No service is start -> restart all services