Current plan is to protect the library loading (which is only used on
VMWare and only to later include additional info in HotSpot error
reports if they happen) with the already existing switch
-XX:ExtensiveErrorReports (default false). The good thing is, that then
it will no longer happen by de
The HotSpot runtime team is investigating it. It was a surprise for them.
New ticket opened by David Holmes:
https://bugs.openjdk.java.net/browse/JDK-8228764
Mail thread starts at:
https://mail.openjdk.java.net/pipermail/hotspot-runtime-dev/2019-July/035431.html
Original implementation ticket
OpenJDK 13/14 introduced change fb5b3981eac:
8222720: Provide extended VMWare/vSphere virtualization related info in
the hs_error file on linux/windows x86_64
On SLES 12 (maybe also other Linuxes) the impl loads
/usr/lib64/libguestlib.so.0 already during JVM startup. That library
depends on
