Page 1 of 1

F5 does not boot after trying to make node as default

Posted: Sun Apr 28, 2019 11:26 am
by heinzford
Hello,

Setup
-------

I'm running eve community edition vm on vmware workstation 12 player.

Laptop

CPU is Intel Core i7-6600U @ 2.60GHz 2.80 GHz
RAM is 16.0GB
Disk is SK hynix SC308 SATA 256GB

VM

RAM is 13.4GB
CPU is 4 cores
HDD is 40GB

root@eve-ng:~# uname -a
Linux eve-ng 4.9.40-eve-ng-ukms-2+ #4 SMP Fri Sep 15 02:07:02 CEST 2017 x86_64 x86_64 x86_64 GNU/Linux



Issue
------

I tried to make my configured F5 BigIP node as default (F5 version and qemu file type below):

root@eve-ng:/opt/unetlab/addons/qemu/bigip-14.1.0.2# ll
total 6273804
drwxr-xr-x 2 root root 4096 Apr 25 12:05 ./
drwxr-xr-x 8 root root 4096 Apr 25 12:24 ../
-rw-r--r-- 1 root root 6424363008 Apr 27 20:18 virtioa.qcow2
root@eve-ng:/opt/unetlab/addons/qemu/bigip-14.1.0.2#


I followed the guide - https://www.eve-ng.net/documentation/ho ... -qemu-node

I was careful to change directory with correct POD ID, UUID and node ID. (I have successfully used this guide before to set a default ASA image.)

I ran the following command : /opt/qemu/bin/qemu-img commit virtioa.qcow2


The first time I got the following error:

"Coroutine re-entered recursively.
Aborted."


I ran the commit command a second time and it successfully committed.


However, now, when I try to boot the original node or create a node in any other lab it does not boot with the following error message:


[ 1.174342] Initramfs unpacking failed: junk in compressed archive
[ 1.270070] systemd[65]: Failed to execute /usr/lib/systemd/system-generators/dracut-rootfs-generator: No such file or directory
[ 1.294173] systemd[1]: Failed to start Create list of required static device nodes for the current kernel.


Please can anyone help me fix the issue and explain what has happened here?

Thanks in advance

Re: F5 does not boot after trying to make node as default

Posted: Sun Apr 28, 2019 5:41 pm
by Uldis (UD)
Actually prepare F5 is very easy,
you have to get original qcow2 image from them and then erpare it

rename original image and place in proper folder

root@eve-ng:/opt/unetlab/addons/qemu/bigip-14.0.0.3-004# ls -l
total 4443524
-rw-r--r-- 1 root root 4550164480 Oct 22 2018 virtioa.qcow2
root@eve-ng:/opt/unetlab/addons/qemu/bigip-14.0.0.3-004#

and after configuration of node, can use commit..
Just one advice after node is committed, use it to another lab is advice to use same MAC address for its mgmt interface.
When you are adding node to topology, you can set custom MAC address for mgmt interface

Visit live helpdesk
https://www.eve-ng.net/live-helpdesk

Re: F5 does not boot after trying to make node as default

Posted: Sun Apr 28, 2019 7:32 pm
by heinzford
Hello,

Thank you for the reply and advice on mgmt MAC address.

I had F5 node working great, but when I tried to set my config as default for any new F5 nodes:

cd /opt/unetlab/tmp/0/<uuid>/<nodeid>/

/opt/qemu/bin/qemu-img commit virtioa.qcow2


All F5 nodes fail to boot up with following output:

[ 1.174342] Initramfs unpacking failed: junk in compressed archive
[ 1.270070] systemd[65]: Failed to execute /usr/lib/systemd/system-generators/dracut-rootfs-generator: No such file or directory
[ 1.294173] systemd[1]: Failed to start Create list of required static device nodes for the current kernel.


How can I diagnose and repair it?

Thank you

Re: F5 does not boot after trying to make node as default

Posted: Mon Apr 29, 2019 5:57 pm
by Uldis (UD)
all simple, image is broken or commited badly

Re: F5 does not boot after trying to make node as default

Posted: Tue Apr 30, 2019 7:37 am
by heinzford
How do I fix it

Re: F5 does not boot after trying to make node as default

Posted: Tue Apr 30, 2019 8:10 am
by Uldis (UD)
get fresh qcow2 image from F5 and try...
in how to are given all steps mate
https://www.eve-ng.net/documentation/ho ... d-f5-bigip