An MR Job can get into stuck because of several reasons. Some of the common reasons are given below
1) Not enough resources in the environment to execute the job
2) Error in the program
3) Problem with the execution environment.
Here the job is running on a Virtual Machine and the performance of the Virtual Machine totally depends on the hardware configuration and performance of your laptop, the reason for this issue might be due to lack of resources. If your laptop has good configuration, increase the resource allocation to the VM.
If the nodemanager is not running, this issue will happen. Check the status of nodemanager in your VM and ensure that it is running properly.
The YARN job will get stuck if it is not able to launch containers for executing the map tasks and reduce tasks. Check the resource manager web UI (localhost:8088) and analyse the containers launched, memory used and the status of the job. You can check the logs also from there. Check if any other jobs are also staying stuck in the cluster.
Try running a sample mapreduce job for finding the wordcount also and see whether it is executing or not.
If you have further queries, please attach the screenshot of the resource manager UI with the status of this job and logs