Yep. This is not recommended on production server. But at home I really not care . Have multi-booting . Windows10 , MacOS, Ubuntu Studio, CentOS and Puppy Linux at same machine
Or in other words VMware program did work (as I confirmed), but in file "microcode-20180108.tgz" Intel Microcode Data File for my i3 3225 was not patched for this vulnerabilities. So this means Intel is launching this file "microcode-20180108.tgz" to public and not all Microcode Data have been updated to fix this vulnerabilities and no mention to this on download page. INTEL HAS LOST ALL CREDIBILITY FOR ME.
You can (not) imagine what will happen when they start to compromise ALL Amazon AWS servers with Spectre. Shared cloud's kernel and memory is the biggest problem here. I already see the lawsuit of Amazon to Intel. And Google too...And everyone else.
It seems 108 is a 'bad' one... Well when updating kernel one can encounter issues. 109 seems to have fixed that... There are still works on Kernel Address Isolation to have Side-channels Efficiently Removed (KAISER) which is a function to prevent exploits... I am on the 4.4 tree as well but have not tried any update yet...I actually wanted to go for the 4.4.110.... ATM I have no patch running....since the read rate of meltdown is guessed like 500 KB/second and through spectre far less I do just reboot my system after I did sensitive transactions just like banking.. In the meantime I try to stay informed until I can notice a reasonable concept and a reasonable combination of measures which do really make sense.