I'm running ESX 6.0 on a HP ProLiant DL380 G7 2x X5650 2.66GHz 6 core CPU 128GB RAM with 1TB HDD.
I've deployed an OVA file (community edition) from the website with the settings (see attachment image) hard disk 1 has 50Gb and disk 2 has 200.
EVE-NG boots absolutely fine. I used WIN SCP to transfer viptela images (version 19.2.099) over and installed using the instructions:
https://www.eve-ng.net/index.php/docume ... mages-set/
However, I modified the folder names as per my version. Eg vtmgmt-19.2.099
I then ran the commands:
/opt/qemu/bin/qemu-img create -f qcow2 virtiob.qcow2 100G
cd
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
vBond,Smart, and edge all run fine.
When adding the vManage node - I have left all the settings as default (4 cpu, 16G ram, etc)
When I try to boot vManage I get the follow message (I can provide a full log if needed)
/dev/vda1: 16 files, 17995/50744 clusters
Mounting /dev/vda1 at /boot
Image found in /dev/vda1 ...
Boot device found in: /dev/vda1
Checking /dev/vda1...
fsck.fat 4.1 (2017-01-24)
/dev/vda1: 16 files, 17995/50744 clusters
Mounting /dev/vda1 at /boot
Waiting for root device ...
Checking signature for /boot/19.2.099/vmlinuz
Unable to continue system boot. Kernel signature verification failed.
The next step I tried was to change the file names virtoa.qcow2 and virtob.qcow2 to hda.qcow2 and hdb.qcow2
The log differs slightly:
/dev/hda1: 16 files, 17995/50744 clusters
Mounting /dev/hda1 at /boot
Image found in /dev/hda1 ...
Boot device found in: /dev/hda1
Checking /dev/hda1...
fsck.fat 4.1 (2017-01-24)
/dev/hda1: 16 files, 17995/50744 clusters
Mounting /dev/hda1 at /boot
Waiting for root device ...
Checking signature for /boot/19.2.099/vmlinuz
Unable to continue system boot. Kernel signature verification failed.
I have followed a few youtube videos and tried using vManage 18.4.4 but have the same result.
My EVE-NG version is 2.0.3-122
I also have plenty of diskspace:
---------------Disk Usage------------------------
Filesystem Size Used Avail Use% Mounted on
udev 50G 0 50G 0% /dev
tmpfs 9.9G 15M 9.9G 1% /run
/dev/mapper/eve--ng--vg-root 238G 3.8G 224G 2% /
tmpfs 50G 0 50G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 50G 0 50G 0% /sys/fs/cgroup
/dev/sda1 472M 119M 329M 27% /boot
The unl_wrapper log file reads:
Feb 12 05:31:44 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Feb 12 05:31:44 INFO: sysctl -w net.ipv6.conf.vunl0_1_0.disable_ipv6=1
Feb 12 05:31:44 INFO: tunctl -u unl0 -g root -t vunl0_1_1 2>&1
Feb 12 05:31:44 INFO: sysctl -w net.ipv6.conf.vunl0_1_1.disable_ipv6=1
Feb 12 05:31:44 INFO: CWD is /opt/unetlab/tmp/0/68975b7f-e125-4f34-996a-92f647116290/1
Feb 12 05:31:44 INFO: starting /opt/unetlab/wrappers/qemu_wrapper -T 0 -D 1 -t "vManager" -F /opt/qemu-2.12.0/bin/qemu-system-x86_64 -d 0 -- -nographic -device virtio-net-pci,netdev=net0,mac=50:00:00:01:00:00 -netdev tap,id=net0,ifname=vunl0_1_0,script=no -device virtio-net-pci,netdev=net1,mac=50:00:00:01:00:01 -netdev tap,id=net1,ifname=vunl0_1_1,script=no -smp 4 -m 16384 -name vManager -uuid f0baa83e-e318-46c8-ac55-2acada56ea14 -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -drive file=virtiob.qcow2,if=virtio,bus=0,unit=1,cache=none -machine type=pc,accel=kvm -cpu host -vga std -usbdevice tablet -boot order=dc -cpu host > /opt/unetlab/tmp/0/68975b7f-e125-4f34-996a-92f647116290/1/wrapper.txt 2>&1 &
Feb 12 05:34:20 INFO: stopping fuser -k -TERM /opt/unetlab/tmp/0/68975b7f-e125-4f34-996a-92f647116290/1 > /dev/null 2>&1
Feb 12 05:34:37 INFO: tunctl -u unl0 -g root -t vunl0_1_0 2>&1
Feb 12 05:34:37 INFO: sysctl -w net.ipv6.conf.vunl0_1_0.disable_ipv6=1
Feb 12 05:34:37 INFO: tunctl -u unl0 -g root -t vunl0_1_1 2>&1
Feb 12 05:34:37 INFO: sysctl -w net.ipv6.conf.vunl0_1_1.disable_ipv6=1
Feb 12 05:34:37 INFO: CWD is /opt/unetlab/tmp/0/68975b7f-e125-4f34-996a-92f647116290/1
Feb 12 05:34:37 INFO: starting /opt/unetlab/wrappers/qemu_wrapper -T 0 -D 1 -t "vManager" -F /opt/qemu-2.12.0/bin/qemu-system-x86_64 -d 0 -- -nographic -device virtio-net-pci,netdev=net0,mac=50:00:00:01:00:00 -netdev tap,id=net0,ifname=vunl0_1_0,script=no -device virtio-net-pci,netdev=net1,mac=50:00:00:01:00:01 -netdev tap,id=net1,ifname=vunl0_1_1,script=no -smp 4 -m 16384 -name vManager -uuid f0baa83e-e318-46c8-ac55-2acada56ea14 -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -drive file=virtiob.qcow2,if=virtio,bus=0,unit=1,cache=none -machine type=pc,accel=kvm -cpu host -vga std -usbdevice tablet -boot order=dc -cpu host > /opt/unetlab/tmp/0/68975b7f-e125-4f34-996a-92f647116290/1/wrapper.txt 2>&1 &
Any help would be gladly appreciated
vManage boot loop - Unable to continue system boot. Kernel signature verification failed.
Moderator: mike
-
- Posts: 3
- Joined: Thu May 27, 2021 5:09 pm
vManage boot loop - Unable to continue system boot. Kernel signature verification failed.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: vManage boot loop - Unable to continue system boot. Kernel signature verification failed.
DO NOT post same thing twice !
-
- Posts: 3
- Joined: Thu May 27, 2021 5:09 pm
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: vManage boot loop - Unable to continue system boot. Kernel signature verification failed.
It looks like image problem actually, might be badly created image, come in eve live chat we can talk for more details