Ready to go Linux image pack for EVE
|Ready to GO Linux Images upload instructions
|Due to very high demand of this section and problems with how to create Linux images under EVE, we are offering ready to go and prepared Linux image pack.
You can choose any of Linux image from the pack below and simply upload into EVE.
2. Download your desirable image
3. Using WinSCP or FileZilla SSH (TCP 22) to your EVE and upload downloaded image to the location: /opt/unetlab/addons/qemu/
4. Using Putty or other telnet client, CLI SSH (TCP 22) to your EVE and go to location:
5. Unzip your uploaded image file, make sure you are using right name of uploaded image. Example for ubuntu desktop image below.
tar xzvf linux-ubuntu-desktop-16.04.4.tar.gz
6. Remove raw zipped image file from EVE
rm -f linux-ubuntu-desktop-16.04.4.tar.gz
7. Fix permissions
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
6. Repeat this procedure for each downloaded image, expecting right image name in commands
Credentials and recommended node settings table:
We have used universal credentials in all our Linux images.
for new Kali 2019.3 linux with RDP enabled: root/toor
How to create own custom Linux host for EVE:
|Custom Linux Images upload instructions
|If you still want create own Linux images, follow the steps below. Watch how to VIDEO. It very similar process like for Windows.
For this you will need real Linux installation CD ISO distro.
We are using: ubuntu-16.04.2-desktop-amd64.iso. Be sure that distro name has not spaces in the filename! Any Linux Server installation has same procedure.
Create new image directory:
mv ubuntu-16.04.2-desktop-amd64.iso cdrom.iso
/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 30G
rm -f cdrom.iso
IMPORTANT: Commit the installation to set it as the default image for further use in EVE-NG:
11. On the left side-bar within the lab in the EVE Web-UI choose “Lab Details” to get your lab’s UUID details: In this example: UUID: 3491e0a7-25f8-46e1-b697-ccb4fc4088a2
12. Find out the POD ID of your used and the Node ID of your newly installed node.
The POD number is assigned to your username, and can be found in the EVE GUI, Management/User Management. The Admin user uses POD number 0 by default.
The Node ID can be obtained by right clicking the node on the topology. In this Example it is 8
12. From the EVE CLI, locate the installed image and commit your changes to be used as default for further use in EVE-NG:
/opt/qemu/bin/qemu-img commit virtioa.qcow2
Advanced instructions on how to make your image smaller in size (sparsify&compress).
13. After you have done all the steps above and your default image is created, you can compress its HDD and make it smaller.
IMPORTANT: for compressing an image you must have sufficient free space on your EVE host, the free space must exceed the total space (30GByte in this example) of the HDD you plan to shrink. The space needed can vary but will be the total space of the disk to be shrunk plus the size of the final sparsified and compressed image. To be safe you should have double the size of the HDD you want to shrink as free space on your EVE host. In our example we needed 35Gbyte of free HDD space. Once this process is done, the temporary file(s) will be deleted and free space reclaimed.
14. From the CLI: go to your windows image directory:
and perform the sparsify command:
eve-sparsify --compress virtioa.qcow2 compressedvirtioa.qcow2
15. This will take some time and another compressed image will be created in the same image directory (win-7test)
16. Rename the compressed image name to virtioa.qcow2:
mv compressedvirtioa.qcow2 virtioa.qcow2
17. now you can test your new compressed image on a lab, just wipe the node and start it.
If the compressed node works fine, you can delete your original source image: