vIOS, IOL and vManage not starting properly even after iourc.txt and fix permissions done.

[rdrive]

Hi,

I can not get vIOS, IOL and vManage to fully start. The usual issues have been dealt with such as creating the license file, -a fixpermissions, moving and correcting the file names to .vmdk along with ensuring they are in the correct locations.

I can create the Nodes for all in a project. For vManage and vIOSs they turn on and go green with access via Telnet to the point "no bootable device" comes up.

For IOL the devices flash on and the "failed to start node" popup comes on.

I've been through the forums, searched Google, worked with a friend who provided the images so I know those are fine and can't locate the issue.

I have done this on a W10 and MacOS build. I am using VMWare Player and VMWare Fusion for the Mac. All my other VMs work fine.

I've checked I've allocated enough space and set up the 100G space.

I've rebuilt all EVE community VMs multiple times.

Help!

[Uldis (UD)]

IOL iourc file must be without any extension .txt or other, and IOL must have fixed permissions.
vIOS and vManage start issue is not related to iourc, but your EVE CPU option Intel VT-X/EPT, it must be enabled on your EVE CPU
Qemu nodes images must be prepared accordingly our How To page.
https://www.eve-ng.net/index.php/documentation/howtos/

[rdrive]

Hi,

I did manage to get the IOL/vIOS working with recreating the iourc file yesterday.

I had previously taken the .txt off and created it in nano and vi to no avail. I did it again from scratch and it worked so yes and thanks that was what looks like a major part of the issue.

I've yet to get vManage functioning but all other parts of the Viptel Suite are.

[rdrive]

With VT-x disabled only IOL boots.

Back with VT-X only vManage won't boot correctly. vSmart, vEdge and vBond all work fine.

I've used three separate versions of vManage and as per the How-Tos and this is what I get for them all:

***************************************

........... No configuration methods s
ucceeded (http://ipxe.org/040ee119)
No more network devices

Booting from ROM...
iPXE (PCI 00:04.0) starting execution...ok
iPXE initialising devices...ok



iPXE 1.0.0+ (0600d) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT

net1: 50:00:00:09:00:01 using virtio-net on 0000:00:04.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net1 50:00:00:09:00:01)................. No configuration methods s
ucceeded (http://ipxe.org/040ee119)
No more network devices

No bootable device.

*******************************************

I'll try anything you suggest, thanks.

[Uldis (UD)]

vmanage need re upload image it looks corrupted, and vManage node contains 2 HDD in the folder,
please read documentation
https://www.eve-ng.net/index.php/docume ... mages-set/

[rdrive]

Hi,

I have done that multiple times. I've followed the How-Tos every single time.

[rdrive]

Right I got it thanks so much.

I had to delete the other versions of vManage, empty their directories and repeat what I'd done although I had made a file spelling issue that fixed it.