There would be a UNIX/windows KM monitoring those VMs, in which case, these entities are identified as STANDALONE because there is data which is collected from within VM as if they are standalone servers, they are really marked the same way from PATROL side.
If these VMs are also coming from some other ETLs in the same entity catalog, the option of skip entity creation could be helpful here.
Indeed VMWare vm running PatrolAgent are identified as STANDALONE because:
configCollector.psl => set ("/UNIX_OS/UNIX_OS@".host."/EntityType","Linux.StandAlone");
There is no test if we run the PatrolAgent within a VMWare instance.
There is a test however if we run in KMV env...
There were 2 Request for Enhancements IP-00044973 for UNIX KM and IP-00044974 for Windows KM but I can't get there status.