CPU model: 12th Gen Intel(R) Core(TM) i7-1260P
RAM: 64GB
HD: 1TB
Eve Version: 5.0.1-19-Community
When using "request system power-off" command, the device ends up at below and just spams the last line forever "128.0.0.1: No route to host". I end up having to stop the switch in eve-ng UI. When starting the host usually it has a disk issue, and I end up having to stop/wipe/start and re-paste my config it as this device doesn't seem to support startup-config like vMX/vQFX. I get this message but sometimes it does boot even after this message "Booting from Junos volume ... Volume was not properly unmounted. Some data may be corrupt. Please run fsck."
I am using vJunos-switch-23.2R1.14 image.
Code: Select all
All buffers synced.
Uptime: 8m23s
umass0: detached
Khelp module "jsocket" can't unload until its refcount drops from 3 to 0.
acpi0: Powering system off
128.0.0.1: No route to host
128.0.0.1: No route to host
128.0.0.1: No route to host
128.0.0.1: No route to host
128.0.0.1: No route to host
128.0.0.1: No route to host
128.0.0.1: No route to host
Code: Select all
root@eve-ng:/opt/unetlab/html/templates/intel# more vJunos-switch.yml
---
type: qemu
description: vJunos-switch
name: vJunos-switch
cpulimit: 4
icon: JunipervQFXre.png
cpu: 4
ram: 5120
eth_name:
- fxp0
- ge-0/0/0
- ge-0/0/1
- ge-0/0/2
- ge-0/0/3
- ge-0/0/4
- ge-0/0/5
- ge-0/0/6
- ge-0/0/7
- ge-0/0/8
- ge-0/0/9
ethernet: 11
console: telnet
qemu_arch: x86_64
qemu_version: 4.1.0
qemu_nic: virtio-net-pci
qemu_options: -machine type=pc,accel=kvm -serial mon:stdio -nographic -smbios type=1,product=VM-VEX -cpu IvyBridge,ibpb=on,md-clear=on,spec-ctrl=on,ssbd=on,vmx=on