• Check your real-time virus scanner configuration and exclude jar files.
  Antivirus exclusion
• Add Java option -Xshareclasses:cacheDir= to your eclipse.ini to target a persistent and well performing network drive for the JVM class cache. Default is in the user home directory, something like C:\Users\MYUSER\AppData\Local\javasharedresources

• Use -configuration option to target a persistent and well performing network drive. By default Eclipse build the OSGI configuration (list of plugins to load) under the user home directory, something like C:\Users\IBM_ADMIN\.eclipse\org.eclipse.platform_4.4.2_2138503820_win32_win32_x86_64. On VDI, the user home might not be persistent and new reconciliation will happen after each VDI logoff/logon
• Use -Declipse.home.location to indicate the Eclipse installation path. If for example the installation was made under “Program Files” but when packaged for VDI it appears as being under something like

  "C:/Users/johndoe/AppData/Local/.../pkgid1234/.../ProgramFilesX64/IBM/SDP" . Eclipse OSGI will then perceive it as a mismatch and will start a reconciliation.

• Do not use -clean option which also forces a reconciliation

...
-install 
C:/Program Files/IBM/SDP 
-configuration I:/rdz-start/ 
-vmargs 
-Xquickstart 
... 
-Xshareclasses:name=IBMSDP_%u,cacheDir=I:/javashrcls 
... 
-Declipse.home.location="C:/Users/johndoe/AppData/Local/.../pkgid1234/.../ProgramFilesX64/IBM/SDP" 

• IDz installation directories like for example c:\Program Files\IBM and c:\Program Files\IBMShared where most of the jar files are located. Check with Inst/allation Manager for the exact location of your shared and installation directories.
• user workspace like c:\workspaces\wrk1
• user home directory for the Eclipse OSGI configuration if the user is not administrator of his machine, like C:\Users\JohnDoe\.eclipse\org.eclipse.platform_4.6.3_1991667125_win32_win32_x86_64\configuration. When the user is administrator, IDz uses the configuration folder under [installation dir]\configuration. But when a user is not administrator or has no write permission on the default configuration directory then Eclipse will create a new configuration under his home directory.You will have to check with your operating system provider where the home directory is located.

• how the anti-virus works: what is scanned and when and how to exclude directories (you may need to contact your anti-virus provider on that)
• the operating system, regional language settings, hypervisor environment, ... which can for example change the location of the user home directory
• where IDz has been installed
• if you accept to not scan these directories (you may need to discuss it with your security team)

# Prints out start level service debug information
org.eclipse.osgi/debug/startlevel=true
# Prints out timing information for bundle activation
org.eclipse.osgi/debug/bundleTime=true
# Debug the loading of message bundles
org.eclipse.osgi/debug/messageBundles=true
# monitor bundle activation
org.eclipse.osgi/monitor/activation=true
org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/reconciler=true
org.eclipse.equinox.p2.core/publisher=true

-vm
jdk/jre/bin/java.exe
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20150204-1316
-install
C:/Program Files/IBM/SDP14
-vmargs
-Xquickstart
-Xms100m
-Xmx1024m
-Xmnx64m
-Xgcpolicy:gencon
-Xscmx96m
-Xshareclasses:name=IBMSDP14_%u
-XX:MaxPermSize=512M
-Xnolinenumbers
-Xcompressedrefs
-Xtrace:none,maximal=mt,output=c:\temp\jvmtrc.log,trigger={method{org/eclipse/core/runtime/internal/adaptor/EclipseAppLauncher.runApplication,jstacktrace},method{org/eclipse/equinox/internal/p2/reconciler/dropins/Activator.start,jstacktrace},method{org/eclipse/equinox/launcher/Main.main,jstacktrace},method{org/eclipse/ui/internal/ide/application/IDEApplication.promptForWorkspace,jstacktrace}},stackdepth=1

"C:\Program Files\IBM\SDP14\eclipsec.exe" -debug c:\temp\.options -consoleLog > c:\temp\startup.log 2>&1