When I start IOL image router it stops within few seconds on EVE

[WaseemShahzad_09]

When I start IOL image router it stops within few seconds on Eve-ng. please help to fix this issue.

[Martin L]

they have their own forum and FAQs you should read/contact Eve.

Regards, ML
**Please Rate All Helpful Responses **

[davd.cachia]

hey guys found a solution

SSH eve and run the Linux command below

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

[mukhtar.aliyev]

 https://www.eve-ng.net/wp-content/uploads/2020/06/EVE-Comm-BOOK-1.09-2020.pdf   Page33: Step 6 : IMPORTANT Open VM Settings. Set the quantity of CPUs and number of cores per socket. Set Intel VT-x/EPT. Hardware Virtualization engine to ON (checked). Once I checked this field, all nodes are started to work.

[ehayric1320]

Our Eve-Pro is installed on a physical server so the above settings don't exist.

I have fixed permissions and followed the license gen instructions but still can't get an image to start.

[shambhu.kumar]

Kindly reach in eve-ng community forum. I am sure you will get resolution.

Thanks

[ehayric1320]

Yes I have done that as well. Just trying to seek help from as many avenues as possible.

[mukhtar.aliyev]

It doesnt matter , just enable virtualization on your server. See logs of server when you start router in EVE-NG. You will see some errors because of it. Also see cookbook of EVE-NG

[shambhu.kumar]

Check the correct license file and.

The newest IOL XE IOS from 2024 original filename does not have extension .bin which is required for EVE-NG. Simply rename your original IOL XE image, adding extension .bin and it is ready to upload in the EVE.

x86_64_crb_linux_l2-adventerprisek9-ms rename it to: x86_64_crb_linux_l2-adventerprisek9-ms.bin

x86_64_crb_linux-adventerprisek9-ms rename it to: x86_64_crb_linux-adventerprisek9-ms.bin

Upload the downloaded image to the EVE using for example FileZilla or WinSCP to:  /opt/unetlab/addons/iol/bin/.

Type following command to fix permissions:

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

IOL images must end with the “.bin” extension and must be executable. EVE-NG Pro has not required to generate iourc license.

License must be stored under the same path. IOU/IOL license is bound to the hostname and domain name of the server. A test should be made to check if IOU/IOL images can run properly.

Google for how to create iourc license file. Bellow is an EXAMPLE how it should look like:

cat /opt/unetlab/addons/iol/bin/iourc
[license]
unl01 = 0123456789abcdef;

[ehayric1320]

Yes I followed the guide exactly. The nodes still start and then stop.

[kamounayman2]

Any updates? I am running into the same issue here and I can't seem to find a solution yet

[ehayric1320]

If I recall correctly, we ended up blowing away all the images and installing fresh. I worked with Eve-helpdesk to pull the images down from their servers via the CLI. If all else fails, try a fresh install of Eve.

You can also try this tool - https://github.com/ishare2-org/ishare2-cli

[hongjiya]

Please try re-generate IOL License like the below

1) Generate IOL License
root@eve-ng:/opt/unetlab/addons/iol/bin# python3 CiscoIOUKeygen.py
*********************************************************************
Cisco IOU License Generator - Kal 2011, python port of 2006 C version
Modified to work with python3 by c_d 2014
hostid=007f0101, hostname=eve-ng, ioukey=7f0343

Add the following text to ~/.iourc:
[license]
eve-ng = 972f30267ef51616;

2) Modify IOL License

root@eve-ng:/opt/unetlab/addons/iol/bin# cat iourc
[license]
eve-ng = 972f30267ef51616;

root@eve-ng:/opt/unetlab/addons/iol/bin# /opt/unetlab/wrappers/unl_wrapper -a fixpermissions

[kamounayman2]

The solution that worked for me, and which I believe is worth sharing, is as follows:

****Please Note****

"Since this is a Registry operation, it’s highly recommended to back up your registry or create a system restore point before proceeding."

1. Open Notepad and paste the following lines into the document:

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard] "RequireMicrosoftSignedBootChain"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity] "WasEnabledBy"=dword:00000000 "Enabled"=dword:00000000

2. Save the file as "Disable_HyperV.reg" and choose "All Files" as the file type.

3. Double-click the saved file to merge it into the registry. When prompted, click "Yes."

4. Once merged, you can delete the file.

5. Finally, go to the settings in your EVE-NG and ensure the "Virtualize Intel VT-x/EPT" or "AMD-V/RVI" option is checked under "Hardware/Processors."

I hope this helps!