Step 1. Inception
- The vendor negotiates a partnership agreement with VMware through the VMware Technology Alliance Partner (TAP) Program: times vary depending on contract negotiations. Ongoing membership in TAP is a requirement of this program.
- The partner is provided access to the relevant materials, development kits and certification kits via this site.
Step 2. Development
- The materials for developing ESXi Server-compatible drivers for the 6.0 release are accessed via either the DDK 6.5 project or the VMK API DDK 6.7 project.
- The partner either develops or updates the driver as necessary: times vary depending on the complexity of the driver and availability of native driver.
- VMware offers technical consulting and assistance for an additional fee. For more information on Development Consulting please contact the IOVP Program Manager.
Step 3. Driver/Device Certification Test
- The partner downloads the relevant Certification Kits and Tools
- IOVP Certification company runs the Functional Verification Tests for driver/device certification: 5-15 days per cycle.
- If a test fails and the failure requires a driver change, the partner fixes the driver and submits a new drop to the project SVN repository, repeat from beginning of Step 3. Note VMware re-verifies the new source and binary.
- If VMware makes any critical changes or additions to tests during the partner’s certification test period, VMware will request the partner to run the new tests.
- VMware offers technical consulting and assistance. Certification support can be purchased from the VMware Store and accessed via My VMware
Step 4. Certification Test Verification
- When a driver and device pass all the Functional Verification tests, the partner submits the results and files a Support Request (SR), both via Work Bench, for VMware to review. IOVP Certification Log Submission entitlements can be purchased from the VMware Store and accessed via My VMware
- VMware verifies test results, informs partner of results: 7-10 days per cycle
- If any results are unclear or incomplete, VMware may request additional information or test reruns. If a test failure results in a driver change and rebuild, repeat from beginning of Step 3
- VMware signs the driver and delivers the signed driver to the partner through the SR. approximately 3-4 days
Step 5. Release
- The information provided with the certification submission is used to update the VMware Compatibility Guide (VCG) with the tested and equivalent and compatible devices.
- VMware publishes the Driver CD to the VMware Downloads Driver & Tools page: 5 days
- VMware updates the VCG: 5 days (concurrent).
- End-to-end certification process time line are 12-15 business days.