Experience with configuring Linux lab on a virtual machine

Recently, I've been working on porting Linux embedded systems on embedded boards, but I don't want to spend too much money on development boards. Then search the Internet for the relevant arm simulator. There are qemu,skyeye,armulator, etc., in accordance with the online tutorial step by step practice, due to the inconsistency of the system environment and other reasons, resulting in deployment of the development environment failed. Inadvertently learned that Docker technology can solve these problems. So just follow this lead on the web to find out, when I saw an article on the use of Linux Lab to complete the process of embedded system software development, I feel finally found a good solution. The relevant links are as follows:

http://tinylab.org/using-linux-lab-to-do-embedded-linux-development/

In accordance with the above link, there are some areas to be aware of, now summarized as follows:

1. When downloading Linux-lab, this command CD Cloud-lab && tools/docker/choose Linux-lab may be slow to download, we can first cloud-lab/labs/ Linux-lab This empty folder delete, and then manually download the Linux-lab, and then manually download the Linux-lab folder and all the contents of the folder to cloud-lab/labs down to replace the original Linux-lab folder
2. Since I am running the Lubuntu system on a virtual machine, the virtual machine is assigned a single core by default, so when the Tools/docker/run command is executed, it appears

This prompt, so that we need to set cpuset-cpuss=0-3 in cloud-lab/configs/linux-lab/docker/limits This file, cpuset-cpus=0, different processor core number and so on.

3. VNC service startup may be slow, we can use the Docker RM Cloud-ubuntu-web, and then tools/docker/export it again. After starting the VNC service, you can use TOOLS/DOCKER/VNC to automatically find the history record.

Experience with configuring Linux lab on a virtual machine