Shulou(Shulou.com)06/01 Report--

Recently, in the network experiment with eve-ng, the powerful function of eve-ng overshadowed the former gns3. However, there is a problem these days: adding a windows 7 host automatically turns gray (stop status) after a few seconds of start.

After some testing, I found out the cause of the problem.

Each virtual device in each lab of eve-ng has an ID, and the ID is incremented according to the order in which the devices are added, starting with 1 by default. My virtual win7 is number 17.

Each lab has a corresponding folder in the system, and there is also a corresponding folder for each device.

For example, the corresponding path to my lab is / opt/unetlab/tmp/0/3154bd2., where 0 represents the admin account, followed by a string of characters that are the code name of lab, and the 1-18 folders in it correspond to each device.

Open the 17 folder and find that the files inside are iourc, nvram and so on, which are similar to those used by the switch.

Open the 18 folder (another working win7 device) and find that there is hda2.qcow2 in it, which is the file to be used when adding a virtual host.

At this point, I probably get it, because ID 17 used to be a Cisco switch, but then I deleted it and added another win7, which caused this problem.

Now that we know the cause of the problem, it is easy to solve it. First delete all the files in folder 17 except wrapper.txt.

Then copy the hda.qcow2 from / opt/unetlab/addons/qemu/win-7-sp1/ to the 17 folder just now (/ opt/unetlab/addons/qemu/win-7-sp1/ is the path where the source image of the virtual machine system is placed, and the final win-7-sp1 is a custom name, and everyone can be different).

Then fix the permissions.

At this time, start this host, successfully enter the system!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.