Hi,
Suggestion: add a comment to Zabbix User Manual v1.8 section 2.6, indicating that vmdk appliance files are in "VMware Workstation/Server" format, and that use with ESX/ESXi/vSphere requires conversion via VMware's free "vCenter Converter Standalone".
Background: The Zabbix appliance is available in vmdx file format. Unfortunately, vmx/vmdk file endings represent at least two semi-incompatible file formats used by various VMware products: VMware Workstation/Server use the same file format as the Zabbix appliance, whereas VMware's newer ESX/ESXi/vSphere do not accept this format, producing error messages such as:
- Device 'Hard disk 1' has a backing type that is not supported. This is a general limitation of the virtual machine's virtual hardware version on the selected host.
- A SparseVer2BackingInfo disk is found but the virtual machine does not support the option.
- Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first? Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/<volume_id>/Zabbix_<version>.vmdk' Module DevicePowerOn power on failed.
- The guest OS ID 'suseGuest' is not valid. Therefore, editing these VM settings is not recommended. Upgrade the VM's virtual hardware to correct problems caused by a virtual disk created for an older VM and added to a newer VM.
- The guest operating system 'suseGuest' is not supported.
So, adding the above-mentioned comment would save trouble-shooting time for Zabbix appliance users with ESX/ESXi/vSphere VMware setups.
Best regards,
Joel
PS: Nice product, Zabbix. :-)
Suggestion: add a comment to Zabbix User Manual v1.8 section 2.6, indicating that vmdk appliance files are in "VMware Workstation/Server" format, and that use with ESX/ESXi/vSphere requires conversion via VMware's free "vCenter Converter Standalone".
Background: The Zabbix appliance is available in vmdx file format. Unfortunately, vmx/vmdk file endings represent at least two semi-incompatible file formats used by various VMware products: VMware Workstation/Server use the same file format as the Zabbix appliance, whereas VMware's newer ESX/ESXi/vSphere do not accept this format, producing error messages such as:
- Device 'Hard disk 1' has a backing type that is not supported. This is a general limitation of the virtual machine's virtual hardware version on the selected host.
- A SparseVer2BackingInfo disk is found but the virtual machine does not support the option.
- Failed to open disk scsi0:0: Unsupported and/or invalid disk type 7. Did you forget to import the disk first? Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/<volume_id>/Zabbix_<version>.vmdk' Module DevicePowerOn power on failed.
- The guest OS ID 'suseGuest' is not valid. Therefore, editing these VM settings is not recommended. Upgrade the VM's virtual hardware to correct problems caused by a virtual disk created for an older VM and added to a newer VM.
- The guest operating system 'suseGuest' is not supported.
So, adding the above-mentioned comment would save trouble-shooting time for Zabbix appliance users with ESX/ESXi/vSphere VMware setups.
Best regards,
Joel
PS: Nice product, Zabbix. :-)
Comment