WARNING THIS IS A DIRTY HACK!
After our Openstack upgrade to Kilo I experienced problems when launching a vSRX 15.1. The image would boot to “Wind River Linux 6.0.0.15” prompt but wouldn’t actually launch the freebsd VM within the nested KVM instance.
The problem is related dmidecode reporting it doesn’t fuly support SMBIOS 2.8
root@localhost:~# dmidecode | head # dmidecode 2.12 SMBIOS 2.8 present. # SMBIOS implementations newer than version 2.7 are not # fully supported by this version of dmideode. blah blah blah
I am guessing various Juniper scripts parse dmidecode output to make sure the VM is the right shape and size before launching the nested KVM VM.
We can solve the issue by creating a wrapper script that will call dmidecode and grep out the warning messages about SMBIOS.
eg.
root@localhost:/# which dmidecode /usr/sbin/dmidecode root@localhost:/# mv /usr/sbin/dmidecode /usr/sbin/dmidecode.orig root@localhost:/# vi /usr/sbin/dmidecode root@localhost:/# cat /usr/sbin/dmidecode #!/bin/bash /usr/sbin/dmidecode.orig $@ | grep -v " SMBIOS implementations newer \| fully supported by this " root@localhost:/# chmod +x /usr/sbin/dmidecode
You can now Shutdown your instance, take a snapshot of the fixed image and use that to launch new vSRX in the future.
Other bits of interest 😉
/usr/sbin/vjunos-console.sh /usr/sbin/platform_hw_functions
Brain Dump 