After figuring out the subject of last post - VMX (version 17.2R1-13) is launching, but the vFP image doesn't appear to be able to launch the image. My login prompt is for the Wind River Linux hypervisor, and the console messages here seem to suggest a failure of the FPC init script to start. The vFPC image file is "vFPC-20170523.img" - apparently a very new release.
Console messages are below:
vfp-vmx1 login: sleep 1 sec
Mount partition /etc on /dev/sda5
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda5): using internal journal
EXT3-fs (sda5): recovery complete
EXT3-fs (sda5): mounted filesystem with ordered data mode
Mount partition /var on /dev/sda6
umount: /var: not mounted
kjournald starting. Commit interval 5 seconds
EXT3-fs (sda6): using internal journal
EXT3-fs (sda6): recovery complete
EXT3-fs (sda6): mounted filesystem with ordered data mode
Setting up a firewall....
ip_tables: (C) 2000-2006 Netfilter Core Team
FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
/home/pfe/riot/phase2_launch.sh: line 209: /var/jnx/card/local/vm_type: No such file or directory
/home/pfe/riot/phase2_launch.sh: line 212: /var/jnx/card/local/type: No such file or directory
0:2345:respawn:/sbin/mingetty tty0
tty0
kernel.core_pattern = /var/crash/core.%e.%t.%p.gz
/var/jnx/card/local/type file not found
i2cid is: 2986 /var/jnx/card/local/slot file not found
slot is: 0 parent: 1045, child: 1046
slot is: 0 Spawning mpcsd with PID 1046
grep: /etc/riot/runtime.conf: No such file or directory
fpc.core.push.sh: no process found
mpc :
tnp_hello_tx: no process found
cat: can't open '/var/jnx/card/local/type': No such file or directory
tx_hello_tx: Failed to get card type defaulting to 0
cat: can't open '/var/jnx/card/local/slot': No such file or directory
tx_hello_tx: Failed to get card slot defaulting to 0
tnp_hello_tx: Board type 0
tnp_hello_tx: Board slot 0
tnp_hello_tx: found interface int
Linux vfp-vmx1 3.10.55-ltsi-rt55-WR6.0.0.13_preempt-rt #1 SMP PREEMPT RT Mon May 22 18:17:09 PDT 2017 x86_64 GNU/Linux
igb_uio: Use MSIX interrupt by default
cat: can't open '/var/jnx/card/local/type': No such file or directory
igb_uio 0000:00:05.0: uio device registered with irq 2e
igb_uio 0000:00:06.0: uio device registered with irq 2f
igb_uio 0000:00:07.0: uio device registered with irq 30
igb_uio 0000:00:08.0: uio device registered with irq 31
OK
0x0BAA
cat: can't open '/var/jnx/card/local/type': No such file or directory
logger: invalid option -- 'c'
Usage:
logger [options] [message]
Options:
-T, --tcp use TCP only
-d, --udp use UDP only
-i, --id log the process ID too
-f, --file <file> log the contents of this file
-h, --help display this help text and exit
-n, --server <name> write to this remote syslog server
-P, --port <number> use this UDP port
-p, --priority <prio> mark given message with this priority
-s, --stderr output message to standard error as well
-t, --tag <tag> mark every line with this tag
-u, --socket <socket> write to this Unix socket
-V, --version output version information and exit
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
config file /etc/riot/init.conf
config file /etc/riot/runtime.conf
Disabled QOS
Unable to open config file /etc/riot/shadow
rte_eth_dev_config_restore: port 0: MAC address array not supported
rte_eth_dev_config_restore: port 1: MAC address array not supported
rte_eth_dev_config_restore: port 2: MAC address array not supported
rte_eth_dev_config_restore: port 3: MAC address array not supported
rte_eth_dev_set_mc_addr_list: Function not supported
rte_eth_dev_set_mc_addr_list: Function not supported
rte_eth_dev_set_mc_addr_list: Function not supported
rte_eth_dev_set_mc_addr_list: Function not supported
Any insight on how to start troubleshooting this? I've verified sufficient RAM and CPUs (4096 is minimum I'm told, and I've assigned four CPU cores). Any other pointers?