vSRXng image issue after apgrade to 2.0.3-105

[glowwarm]

Hi

After upgraded to EVE-NG 2.0.3-105, vSRXNG images starting slow and can't boot to system. I tried other images like vMXs and vQFXs all good. Please see error message below. Thank you!

Loading JUNOS chassis module
chassis_init_hw_chassis_startup_time: chassis startup time 0.000000
Kernel thread "wkupdaemon" (pid 53) exited prematurely.
Trying to mount root from ufs:/dev/vtbd0s1a
NMI ISA 30, EISA ff
NMI ... going to debugger
[thread pid 12 tid 100004 ]
Stopped at acpi_timer_read+0x13: jmp acpi_timer_read+0x17
db>

Tony

[Uldis (UD)]

we are going with new requirements of vendor different version, thats why older srx can have issues with qemu versions.
new eve community has set by default newest qemu 4.1.0 for juniper devices.
If you still have issues you can try this:

add node on topology and start or for older nodes before start it, set older qemu for vsrx.

[glowwarm]

Thanks for the quick responds. One more question, how can I change default "QEMU custom options"? I found that I need to add some cpu flags to make it working probably. If I can change the default options, I don't have to change it for every time. Thank you.

[Uldis (UD)]

qemu options you can set by default in
/opt/unetlab/html/templates/
editing vsrxng template you can set any qemu version to be as default

btw best from new srx is 19.2.R1.8
works just flawless on any eve new templates

[glowwarm]

Hi Kronicklez

I was using vsrxng-19.4R1.10. But it's good now. I was given not enough memory and CPUs.

Tony