Huawei AR1000v Failed to boot up
Posted: Tue Mar 24, 2020 9:59 am
Hi Team,
Glad to know huawei AR1000v has officially been supported on EVENG. When i try to build a lab demo on my PC and each AR1000v node i assign 1 vCPU with 2 GB RAM, but AR1000v cannot boot up and keeps rebooting.
Here is more information.
My PC hardware/OS:
OS: Windows 7 SP1, running EVENG on vmware workstation 14 Pro.
CPU: intel I7-4700MQ/16G RAM/SSD 120GB
MY EVENG version:
root@eve-ng:~# uname -a
Linux eve-ng 4.20.17-eve-ng-ukms+ #2 SMP Wed Jun 5 08:18:06 CEST 2019 x86_64 x86_64 x86_64 GNU/Linux
Error Messages :
====================================================
=================================================
any suggestions would be appreciated.
Regards,
Li
Glad to know huawei AR1000v has officially been supported on EVENG. When i try to build a lab demo on my PC and each AR1000v node i assign 1 vCPU with 2 GB RAM, but AR1000v cannot boot up and keeps rebooting.
Here is more information.
My PC hardware/OS:
OS: Windows 7 SP1, running EVENG on vmware workstation 14 Pro.
CPU: intel I7-4700MQ/16G RAM/SSD 120GB
MY EVENG version:
root@eve-ng:~# uname -a
Linux eve-ng 4.20.17-eve-ng-ukms+ #2 SMP Wed Jun 5 08:18:06 CEST 2019 x86_64 x86_64 x86_64 GNU/Linux
Error Messages :
====================================================
Code: Select all
systemd[1]: Reached target Sockets.
systemd[1]: Starting Journal Service...
systemd[1]: Started Journal Service.
systemd-udevd[96]: starting version 215
systemd-fsck[141]: /dev/vda1: clean, 257/128016 files, 224177/512000 blocks
EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null)
systemd-fsckEXT4-fs (vda2): mounting ext3 file system using the ext4 subsystem
[147]: /dev/vda2: clean, 288/572832 files, 132994/1246464 blocks
EXT4-fs (vda2): mounted filesystem with ordered data mode. Opts: (null)
systemd-journald[94]: Received request to flush runtime journal from PID 1
random: nonblocking pool is initialized
systemd[1]: Unit failure-recored@multi-user.service entered failed state.
ipmi message handler version 39.2
IPMI System Interface driver.
ipmi_si: Adding default-specified kcs state machine
ipmi_si: Trying default-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
ipmi_si: Interface detection failed <<<<<<<<<<
ipmi_si: Adding default-specified smic state machine
ipmi_si: Trying default-specified smic state machine at i/o address 0xca9, slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Adding default-specified bt state machine
ipmi_si: Trying default-specified bt state machine at i/o address 0xe4, slave address 0x0, irq 0
ipmi_si: Interface detection failed
ipmi_si: Unable to find any System Interface(s)
modprobe: ERROR: could not insert 'ipmi_si': No such device <<<<<<<<
ipmi device interface
Bootloader creation Data : Jul 13 2018, 01:19:09
Boot Fail times = 1
Now boot from flash:/ar.cc, please wait......
squashfs_cache_init: sqcachesize=3.
excutive app squsdhfs
start monitor ...
sMssMemToalSize = 4040432
4 serial
1 i8042
24 virtio
25 virtio
14 virtio
15 virtio
Monitor Bsp so creation Data : May 20 2019, 20:50:29
FLASH_CreateFlashFile /mnt/misc/flashfile
Create monitor process
Monitor Bsp so creation Data : May 20 2019, 20:50:29
FLASH_CreateFlashFile /mnt/misc/flashfile
Product enviroment init ... ok
start fwm ...
Now in inject process...
No inject vm_init_para.ini
start evm ...
/dev/shm/fwm: /mnt/squash/lib/libcrypto.so.1.0.0: no version information available (required by /usr/lib/i386-linux-gnu/libssl.so.1.0.0)
/dev/shm/fwm: /mnt/squash/lib/libcrypto.so.1.0.0: no version information available (required by /usr/lib/i386-linux-gnu/libssl.so.1.0.0)
/dev/shm/fwm: /mnt/squash/lib/libcrypto.so.1.0.0: no version information available (required by /usr/lib/i386-linux-gnu/libssl.so.1.0.0)
/dev/shm/fwm: /mnt/squash/lib/libcrypto.so.1.0.0: no version information available (required by /lib/i386-linux-gnu/libthrift_c_glib.so.0)
cp: cannot stat '/mnt/squash/dev/shm/netopeer': No such file or directory
watchdog watchdog0: watchdog did not stop!
watchdog watchdog0: watchdog did not stop!
reboot: Restarting system
any suggestions would be appreciated.
Regards,
Li