Device Start and Stop Immediately in eve-ng.

[mondrunio]

Hello guys could you be so kind and assist me with this issue.

I am trying to create some labs for Cisco CCNA Exam.

I am using: Lenovo 5 PRO with AMD Ryzen 7 5800H, 16GB of RAM and M.2 SSD disc.

I added 2 qemu images using this procedure created by David:
https://www.eve-ng.net/index.php/docume ... from-virl/

Images:
vios-adventerprisek9-m.vmdk.SPA.157-3.M3.qcow2
viosl2--adventerprisek9-m.ssa.high_iron_20200929.qcow2

EVE-NG on VMware Workstation Pro 17

When I add router or switch to project and start device, it start and stop immediately. I have no idea how to resolve that problem.

What I've already tried:
disabled - Virtualize Intel VT-x/EPT or AMD-V/RVI
disabled - Hyper-V
disabled - slide channel mitigations
disabled - Windows subsystem for Linux

Is this even possible with the AMD Ryzen 7 5800H processor?

[Uldis (UD)]

did you rename it properly inside the image folder?

Code: Select all

root@eve-ng-master:/opt/unetlab/addons/qemu/vios-adventerprisek9-m.SPA.159-3.M6# ls
virtioa.qcow2
root@eve-ng-master:/opt/unetlab/addons/qemu/vios-adventerprisek9-m.SPA.159-3.M6#

[mondrunio]

Sure, according to the documentation, after that I added permissions as well:

vios | L3 vIOS Cisco Router | virtioa
viosl2 | L2 vIOS Cisco SW | virtioa

/opt/unetlab/wrappers/unl_wrapper -a fixpermissions

[jkjkrules]

I'm having this same issue tried uninstalling and reinstalling but no luck

[Uldis (UD)]

2 problem can be here:
you have not enabled nested virtualization:
to check on eve cli must see:

Code: Select all

root@eve-master:~# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
root@eve-master:~# 

if this is OK, you simply loaded wromg image or made it badly

[patrick@esoltani.com]

Hi All,
vios and viptela images do not stay up. I meticulously have walked and rewalked the steps in the cookbook, still the node starts and immediately stops. BTW, IOL is working FINE on the same system.

root@myeve:/root# dpkg -l eve-ng
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-==============================================
ii eve-ng 5.0.1-19 amd64 A new generation software for networking labs.
root@myeve:/root#

root@myeve:/opt/unetlab/addons/qemu/vios-adventerprisek9-m.SSA.high_iron_20200929# file virtioa.qcow2
virtioa.qcow2: VMware4 disk image
root@myeve:/opt/unetlab/addons/qemu/vios-adventerprisek9-m.SSA.high_iron_20200929#

Appreciate any pointers as I have exhausted anything I could fined via search and config editing.


here is the syslog when firing the node and have searched low/high to no avail.
============================================================
Jun 29 14:05:13 myeve systemd-networkd[831]: vunl0_5_0: Link DOWN
Jun 29 14:05:13 myeve kernel: [ 9197.360525] vnet0_4: port 1(vunl0_5_0) entered disabled state
Jun 29 14:05:13 myeve kernel: [ 9197.361311] device vunl0_5_0 left promiscuous mode
Jun 29 14:05:13 myeve kernel: [ 9197.361316] vnet0_4: port 1(vunl0_5_0) entered disabled state
Jun 29 14:05:13 myeve networkd-dispatcher[1712]: WARNING:Unknown index 34 seen, reloading interface list
Jun 29 14:05:13 myeve systemd-udevd[21114]: Using default interface naming scheme 'v245'.
Jun 29 14:05:13 myeve systemd-udevd[21114]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 29 14:05:13 myeve systemd-udevd[21114]: vunl0_5_0: Could not generate persistent MAC: No data available
Jun 29 14:05:13 myeve systemd-networkd[831]: vunl0_5_0: Link UP
Jun 29 14:05:13 myeve systemd-networkd[831]: vnet0_4: Gained carrier
Jun 29 14:05:13 myeve kernel: [ 9197.435934] vnet0_4: port 1(vunl0_5_0) entered blocking state
Jun 29 14:05:13 myeve kernel: [ 9197.435940] vnet0_4: port 1(vunl0_5_0) entered disabled state
Jun 29 14:05:13 myeve kernel: [ 9197.436007] device vunl0_5_0 entered promiscuous mode
Jun 29 14:05:13 myeve kernel: [ 9197.436050] vnet0_4: port 1(vunl0_5_0) entered blocking state
Jun 29 14:05:13 myeve kernel: [ 9197.436053] vnet0_4: port 1(vunl0_5_0) entered forwarding state
Jun 29 14:05:13 myeve systemd-networkd[831]: vunl0_5_1: Gained carrier
Jun 29 14:05:13 myeve systemd-networkd[831]: vnet0_5: Gained carrier
Jun 29 14:05:13 myeve kernel: [ 9197.446552] vnet0_5: port 2(vunl0_5_1) entered blocking state
Jun 29 14:05:13 myeve kernel: [ 9197.446558] vnet0_5: port 2(vunl0_5_1) entered forwarding state
Jun 29 14:05:13 myeve systemd-networkd[831]: vunl0_5_1: Link DOWN
Jun 29 14:05:13 myeve systemd-networkd[831]: vunl0_5_1: Lost carrier
Jun 29 14:05:13 myeve kernel: [ 9197.453567] vnet0_5: port 2(vunl0_5_1) entered disabled state
Jun 29 14:05:13 myeve kernel: [ 9197.453990] device vunl0_5_1 left promiscuous mode
Jun 29 14:05:13 myeve kernel: [ 9197.453995] vnet0_5: port 2(vunl0_5_1) entered disabled state
Jun 29 14:05:13 myeve networkd-dispatcher[1712]: WARNING:Unknown index 35 seen, reloading interface list
Jun 29 14:05:13 myeve systemd-udevd[21114]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 29 14:05:13 myeve systemd-udevd[21114]: vunl0_5_1: Could not generate persistent MAC: No data available
Jun 29 14:05:13 myeve systemd-networkd[831]: vunl0_5_1: Link UP
Jun 29 14:05:14 myeve kernel: [ 9197.517281] vnet0_5: port 2(vunl0_5_1) entered blocking state
Jun 29 14:05:14 myeve kernel: [ 9197.517287] vnet0_5: port 2(vunl0_5_1) entered disabled state
Jun 29 14:05:14 myeve kernel: [ 9197.518175] device vunl0_5_1 entered promiscuous mode
Jun 29 14:05:14 myeve kernel: [ 9197.518337] vnet0_5: port 2(vunl0_5_1) entered blocking state
Jun 29 14:05:14 myeve kernel: [ 9197.518341] vnet0_5: port 2(vunl0_5_1) entered forwarding state
Jun 29 14:05:14 myeve kernel: [ 9198.409146] vnet0_4: port 1(vunl0_5_0) entered disabled state
Jun 29 14:05:14 myeve kernel: [ 9198.409332] vnet0_5: port 2(vunl0_5_1) entered disabled state
Jun 29 14:05:15 myeve systemd-networkd[831]: vnet0_4: Lost carrier
Jun 29 14:05:15 myeve systemd-networkd[831]: vnet0_5: Lost carrier

[Uldis (UD)]

It looks simply not enabled nested virtualization on your EVE

your eve output must show:

Code: Select all

root@eve-master:~# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
root@eve-master:~# 

[patrick@esoltani.com]

Did not find any answers anywhere; Bard/ChatGPT and other AIs failed too!!!
I ended up using OVA file and built a brand new setup; just in case another soul tear their hair out trying to figure this out.

Hi All,
vios and viptela images do not stay up. I meticulously have walked and rewalked the steps in the cookbook, still the node starts and immediately stops. BTW, IOL is working FINE on the same system.

root@myeve:/root# dpkg -l eve-ng
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-==============================================
ii eve-ng 5.0.1-19 amd64 A new generation software for networking labs.

[Uldis (UD)]

EVE is not installed at all...

[Kosmoskatten]

Have the same issue with eve on ESXi where I cant get Qemu to run after I did a upgraded in April. Tried to troubleshoot but could not find a solution, not as linux savvy as needed so reinstalled and moved license, same problem.

Been busy so I left it as is and did an upgrade today hoping to solve the problem, it did not. First installation is probably a mess after my troubleshooting (cant upgrade), but the second installation did upgrade most of it's packages but is still saying that eve is not installed.

Code: Select all

root@eve-ng:~# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

root@eve-ng:~# dpkg -l eve-ng
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
un  eve-ng         <none>       <none>       (no description available)

If I do a general list instead i get this (omitted all except eve)

Code: Select all

ii  eve-ng-dockers                        5.0-eve-ng                            amd64        Dockers Eve-NG PRO compatible
ii  eve-ng-dynamips                       5.0.1-1                               amd64        Dynamips files for Eve-NG.
ii  eve-ng-pro                            5.0.1-106                             amd64        A new generation software for networking labs.
ii  eve-ng-pro-guacamole                  5.0.1-1                               amd64        Guacamole for UNetLab/EVE-NG
ii  eve-ng-qemu                           5.0.1-1                               amd64        QEMU files for Eve-NG.
ii  eve-ng-schema                         5.0.1-1                               amd64        Database schema for UNetLab/EVE-NG
ii  eve-ng-vpcs                           5.1-eve-ng                            amd64        vpcs Eve-NG compatible

Errors during upgrade (repeated twice then moved to next part) :

Code: Select all

Updating satellite(s)... PHP Notice:  Trying to access array offset on value of type null in /opt/unetlab/html/includes/init.php on line 69
PHP Warning:  Invalid argument supplied for foreach() in /opt/unetlab/html/includes/init.php on line 69
PHP Warning:  file_get_contents(/opt/unetlab/platform): failed to open stream: No such file or directory in /opt/unetlab/html/includes/init.php on line 114
Jul 02 20:54:35 Jul 02 20:54:35 Online Check state: Valid
PHP Notice:  Trying to access array offset on value of type null in /opt/unetlab/html/includes/init.php on line 69
PHP Warning:  Invalid argument supplied for foreach() in /opt/unetlab/html/includes/init.php on line 69
PHP Warning:  file_get_contents(/opt/unetlab/platform): failed to open stream: No such file or directory in /opt/unetlab/html/includes/init.php on line 114

I will probably try to reinstall again to see if this is solved in a later release but if anyone have some insight it's always good, reinstalling and moving is not that fun.

Just a note, I have been using eve since 2017 (unetlab before that) and is a pro user since 2019 and this is the first major problem I have encountered.