I'm trying to spin a vsrx in eve-ng without success so far.
My setup:
- eve-ng 2.0.3-105
- Bare metal
- Linux eclipse 4.20.17-eve-ng-ukms+ #2 SMP Wed Jun 5 08:18:06 CEST 2019 x86_64 x86_64 x86_64 GNU/Linux
- CPU0: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz (family: 0x6, model: 0x2c, stepping: 0x2)
- Memory: 49374900K/50318360K available (12293K kernel code, 2268K rwdata, 4128K rodata, 2444K init, 5400K bss, 943460K reserved, 0K cma-reserved)
Code: Select all
Filesystem Size Used Avail Use% Mounted on
udev 24G 0 24G 0% /dev
tmpfs 4.8G 18M 4.7G 1% /run
/dev/mapper/eclipse--vg-root 548G 69G 451G 14% /
tmpfs 24G 0 24G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 24G 0 24G 0% /sys/fs/cgroup
/dev/sda1 720M 131M 553M 20% /boot
tmpfs 4.8G 0 4.8G 0% /run/user/1000First thing that ALWAYS happens is a panic at this point and then the system reboots:
Trying to mount root from cd9660:/dev/md0.uzip []...
mode = 0100644, inum = 6910, fs = /.mount
panic: ffs_valloc: dup alloc
cpuid = 1
Uptime: 15s
Automatic reboot in 15 seconds - press a key on the console to abort
--> Press a key on the console to reboot,
--> or switch off the system now.
This seems to be associated with a disk error, which apparently is fixed as below, and then the system reboots again:
Trying to mount root from cd9660:/dev/md0 []...
** /dev/gpt/oam
** Last Mounted on /.mount
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
47 files, 30675 used, 4161811 free (3 frags, 520226 blocks, 0.0% fragmentation)
***** FILE SYSTEM IS CLEAN *****
Software recovery
No recovery snapshot available
Waiting (max 60 seconds) for system process `vnlru' to stop... done
Waiting (max 60 seconds) for system process `bufdaemon' to stop... done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining... 0 done
All buffers synced.
Uptime: 3s
Rebooting...
But I do need to stop the boot process and run a file system check using the menu options:
Main Menu
1. Boot [J]unos volume
2. Boot Junos volume in [S]afe mode
3. [R]eboot
4. [ B ]oot menu
5. [M]ore options. <<<<<
Options Menu
1. Recover [J]unos volume
2. Recovery mode - [C]LI
3. Check [F]ile system. <<<<<<
4. Enable [V]erbose boot
5. [ B ]oot prompt
6. [M]ain menu
...
...
Running: fsck_ufs -y /dev/gpt/junos
** /dev/gpt/junos
** Last Mounted on /.mount
** Phase 1 - Check Blocks and Sizes
INCORRECT BLOCK COUNT I=637 (2 should be 0)
CORRECT? yes
INCORRECT BLOCK COUNT I=6910 (2 should be 0)
CORRECT? yes
INCORRECT BLOCK COUNT I=6917 (12 should be 0)
CORRECT? yes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=637 OWNER=0 MODE=100644
SIZE=0 MTIME=Mar 11 15:42 2020
CLEAR? yes
UNREF FILE I=6910 OWNER=0 MODE=100644
SIZE=0 MTIME=Mar 11 15:28 2020
CLEAR? yes
UNREF FILE I=6917 OWNER=0 MODE=100644
SIZE=0 MTIME=Mar 11 15:28 2020
CLEAR? yes
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? yes
SUMMARY INFORMATION BAD
SALVAGE? yes
BLK(S) MISSING IN BIT MAPS
SALVAGE? yes
6498 files, 1013206 used, 12572998 free (230 frags, 1571596 blocks, 0.0% fragmentation)
***** FILE SYSTEM MARKED CLEAN *****
***** FILE SYSTEM WAS MODIFIED *****
File system repair
Type 'exit' when done.
# exit
After this step, the system boots and go further up until it crashes again:
pci-hgcomdev module loaded
Loading BCMSDK module.....
veriexec: no fingerprint for file='/sbin/kats/cannot-exec' fsid=174 fileid=49356 gen=1 uid=0 pid=5244
lag enhanced disabled 0
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x3b
fault code = supervisor read data, page not present
instruction pointer = 0x20:0xffffffff81307502
stack pointer = 0x0:0xfffffe00002af470
frame pointer = 0x0:0xfffffe00002af520
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 5940 (irsd)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 2m33s
Dump failed. Partition too small.
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
And then everything is started over again.
This behavior is consistent with ALL combinations for the Junos images and qemu.
I do have other nodes such as qfx, vmx, linux that are running without any issues. But there is something missing for the vsrx that I cannot find out.
Thanks for your help.