Support and News Forum

Been trying to load the L2 image: viosl2-adventerprisek9-m-15.2-2017032.qcow2

Currently running eve-ng via ESXi 6.5, 2 vcpus and 16 gb ram

However I've tried multiple things but nothing seems to make it boot.

In default tpl for qemu, architecture and nic, but nothing loads.

Try changing the tpl for 4.1.0 and others but still nothing, then try changing tpl (i386) for just i386 and still nothing. However if I change the qemu nic to e1000-8245em it comes up with trying to configure the network devices:

net0: 50:00:00:07:00:00 using 82545em on 0000:00:02.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 50:00:00:07:00:00).....

It keeps repeating, eventually I get this:
Booting from Floppy...
Boot failed: could not read the boot disk

Booting from Hard Disk...
Boot failed: could not read the boot disk

No bootable device.

Also seen this in the syslog:

Dec 22 00:43:51 eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_7_1
Dec 22 00:43:51 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_7_1
Dec 22 00:43:51 eve-ng systemd-udevd[6594]: Could not generate persistent MAC address for vunl0_7_1: No such file or directory

I have a sneaking suspicion it is to do with the hdd move, as I've used this in gns3 and under ide it loads no worries.

Now before anyone asks I have virtualisation pass through enabled, I cant seem to add vhv.enable = "TRUE" as it kills the vm as it cant find the vmx file after I edit it in esxi command line, not sure if this makes a difference, also I do run iol images just fine both l2 and l3

you simply did not make image properly.
Your output is saying that image naming is wrong.

https://www.eve-ng.net/index.php/docume ... from-virl/
even david Bombal video is attached to showing how you must make this image.

Next x2 vCPU is very short for eve.
Esxi EVE VM CPU settings are:
8/1, 16/1, 24/1, 32/1....

Thanks for that, I didnt realise it was so finicky about file naming! Funnily enough after i made the corrections to the folder naming, (and correcting permissions) it came up as a vios router! But the image was fine and dandy.

Its now running just fine. This is more so just to test eve-ng out, and comparing it to GNS3 web ui - frankly both are very good, but with some subtle differences.

Thanks again!!

if your node booted as router, means again you messed up something with names before and image loading in proper folder.
One tip:
To be sure if your images starts from scratch what you had loaded, use right click on node/wipe.
This will clean node NVRAM, and will boot image as factory default.
If you changed image version in node edit,
wipe is a must, to force node boot from new image..

Big helper for EVE is Cookbook.
Community
https://www.eve-ng.net/index.php/docume ... -cookbook/

Profesional
https://www.eve-ng.net/index.php/docume ... -cookbook/

Uldis