Fixed
Created: Nov 7, 2019
Updated: Dec 11, 2019
Resolved Date: Dec 11, 2019
Found In Version: 10.19.45.1
Fix Version: 10.19.45.2
Severity: Standard
Applicable for: Wind River Linux LTS 19
Component/s: Userspace
It has been observed that OverC networking can fail at startup, especially when running OverC with QEMU without KVM acceleration. If network connectivity between the OverC cubes or to external devices, you can verify the failure by running 'c3 list' in dom0, if cube-vrf does not have an IP address you have hit this situation. To resolve this reboot the VM and if possible use KVM.
See comments for ways to minimize the likelihood that his happens.
./setup.sh --distro wrlinux-overc --dl-layers --no-recommend --machine genericx86-64
. ./environment-setup-x86_64-wrlinuxsdk-linux
. ./oe-init-build-env
BB_NO_NETWORK ?= '0'
MACHINE=qemux86-64 bitbake cube-vrf cube-dom0 cube-essential cube-server cube-builder-initramfs cube-builder cube-desktop
bitbake grub-native jq-native
bitbake build-sysroots
cp ../layers/wrlinux/wrlinux-overc/bin/* .
sudo PATH=$PWD/tmp/sysroots/x86_64/usr/bin:$PWD/tmp/sysroots/x86_64/usr/sbin:$PATH ../overc-installer/sbin/cubeit --disk-size 15G --force --config `pwd`/image-live.sh --artifacts `pwd`/tmp/deploy/images/genericx86-64 boot.img
stty -onlcr ; $PWD/tmp/sysroots/x86_64/usr/bin/qemu-system-x86_64 -drive file=boot.img,if=virtio -m 2000 -nographic -vnc :3 -serial mon:stdio -netdev type=user,id=h1,hostfwd=tcp::4440-10.0.2.15:22,hostfwd=tcp::4441-10.0.2.15:2222,hostfwd=tcp::8080-10.0.2.15:8080 -device e1000,netdev=h1,mac=00:55:55:01:01:01,romfile= -usbdevice tablet -cpu qemu64,+ssse3,+sse4.1,+sse4.2,+x2apic; stty onlcr ; reset
In dom0:
root@cube-dom0:~# c3 add docker://debian
