Bare Metal install will not run any images except built in

[jonfon]

Hello All
I have installed the bare metal version from the Download site. I have a Cisco ucs m4 with two xeon Processors and 700 gig of ram. 6 TB of Hard drive space.

I booted using the uhci usb drive per the instructions and it loaded ok . I did have an issue with the TPM so I removed it and the error was removed.
AS I noted I am able to access the GUI via the browser and have installed the nodes per the information provide on the community install pdf without issue.
I also confirm the images are working using the "qemu-system-x86_64 -m 2G -hda virtioa.qcow2 -enable-kvm -nographic" and it loaded the l3 image without issue.

If I use the same image on eve-ng and start it via html-5 or native the device seems to start and then stop. If logout and enter with HTML-5 and start the router or switch
I get a black screen with "0,vios" in the corner. if run the switch it will show "0;switch" and never start. I read the whole document on bare metal install and it does not
provide a way to look at the error in the logs section that give me an understanding what is happening to the image.

if you can provide me with some information or were I can look at to get this issue resolved.

I have done the fix permission command and that did not resolve this issue.

thank you

jon

[rusty725]

show output of kvm-ok

[jonfon]

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

root@sdc-eve-ng:/# /usr/bin/qemu-system-x86_64 --version
QEMU emulator version 6.2.0 (Debian 1:6.2+dfsg-2ubuntu6.24)
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

I notice when I change the qemu from the tpl(2.4.0) to 6.2.0 it seems to get some movement but I have change the setting from 1.3.0 to 6.0.0 and it still does not load it will look for a boot information and will run thur the network cards until it has not more to run. I selected the qemu arch from i386 , x86_64 and tpl(x86_64) with the use of the qemu nic of tpl(e1000). QEMU custom options is "-machine type=pc,accel=kvm -serial mon:stdio -nographic -no-user-config -nodefaults -rtc base=utc -cpu host"

I would also like to know were I can get a log information when this image loads so I can lookup the errors.


data provided below

net0: 50:00:00:01:00:00 using 82540em on 0000:00:02.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 50:00:00:01:00:00)................. No configuration methods s
ucceeded (http://ipxe.org/040ee119)
No more network devices

Booting from ROM...
iPXE (PCI 00:03.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:01:00:01 using 82540em on 0000:00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net1 50:00:00:01:00:01)................. 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

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

Booting from ROM...
iPXE (PCI 00:05.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

net3: 50:00:00:01:00:03 using 82540em on 0000:00:05.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net3 50:00:00:01:00:03)................. No configuration methods s
ucceeded (http://ipxe.org/040ee119)
No more network devices

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

No bootable device.

[Uldis (UD)]

For the best and fastest support or any other questions please join in the EVE-NG live support:
https://webchat.eve-ng.net/login/
Use your Gmail account to login, or create new chat account with own email.

[jonfon]

I also tried with an ASAv Image and I get the same it looking for boot information. per the web its not located the correct image file but I have change it to the standards.

If we look at the ASAv and folder I named the image per the instruction

root@sdc-eve-ng:/opt/unetlab/addons/qemu# ls -l *

asav-9-16-4-19:
total 330820
-rw-r--r-- 1 root root 338755584 Feb 7 21:17 virtioa.qcow2

vios-adventerprisek9-m-15.6.2T:
total 125444
-rw-r--r-- 1 root root 128450560 Feb 6 21:25 virtioa.qcow2

vios-adventerprisek9-m.spa.159-3.m2:
total 48492
-rw-r--r-- 1 root root 49655808 Feb 6 21:28 virtioa.qcow2


let me know if there is a setting i missed or naming that is not correct. If I run the image from the cli with the qemu command it works fine. there are a few qemu versions to choose from

root@sdc-eve-ng:/opt# ls
ovf qemu-1.3.1 qemu-2.12.0 qemu-2.4.0 qemu-2.6.2 qemu-4.1.0 qemu-6.0.0 qemu-8.2.1 vpcsu
qemu qemu-2.0.2 qemu-2.2.0 qemu-2.5.0 qemu-3.1.0 qemu-5.2.0 qemu-7.2.9 unetlab