Installation and first checks
Install the module, then verify the connection, cron and licence status.
Before you start
- A valid WISECP installation; at least 5.0-beta.2, verified on 5.0-beta.3.
- PHP 8.1+ with cURL, DOM and OpenSSL. mbstring and ZIP are recommended.
- ESXi 7.0 / 8.0 with a paid or evaluation licence that provides write API access. The read-only free Hypervisor licence is not suitable for provisioning.
- Access from the WISECP server to ESXi on 443/TCP; correct DNS and server time.
- Prepared operating system templates that include VMware Tools / open-vm-tools.
- Separate backups of files, the database and VM data.
Upload the package
Get the installation ZIP from your Hostimor licence service or from the WISECP Marketplace; use only the signed package.
- Take a backup of the WISECP files and database.
- Upload the package through Tools → Addons → Upload New Addon, or merge the
coremio/directory from the ZIP into the WISECP root directory. - Check that the
coremio/modules/Servers/VMwareESXi/directory has been created. - Open the Products → Hosting & Servers → Hostimor | VMware ESXi Management page. Administrators with the product management privilege can see the page; operations that touch customer virtual machines also require service privileges.
- Use the page’s Settings button to save the update key of your service (a WISECP Marketplace installation does not have this field). Do not share the key in screenshots or logs.
1.8.0 (in WISECP review): the package installs into the coremio/modules/Servers/HostimorVMwareESXi/ directory and the update key step is dropped; the licence is verified against the domain of your WISECP licence.
Cron and licence
Run the cron command shown in the WISECP system settings every minute. Provisioning completion, template imports and migration jobs are processed through this queue.
On the Hostimor | VMware ESXi Management → Licence and Updates screen, review the domain, licence status, installed versions, compatibility and package integrity. Re-check checks the licence; it does not extend the licence term.
First test service
Create a new, empty test VDS. Check that the service number, ESXi, CPU, RAM, disk, IP and operating system selection are correct. Wait for the operation to finish, then verify VMware Tools, networking and the client area. Do not use existing customers’ VMs to test the installation.