I am testing, 2X VDI. Its look nice. Only it is not working, properly. Error log: failed to power off guest using soap SOAP 1.1 fault: "":ServerFaultCode [no subcode]|"fault.RestrictedVersion.summary"|Detail: |
The vSphere SDK is restricted to read-only operations when connecting to the free version of ESXi[1], hence an error is produced when attempting certain VDI operations like starting a virtual machine. http://goo.gl/LMgVF (refer to ESXi notes in the "CLI-Based Configuration" section) Thanks
So ESXi 4.1 is not supported then? we have tried with 2 hosts 4.0 and 4.1 and receive the same soap errors?
Quoting from : Free ESXi (or VMware vSphere Hypervisor 4.1) limitations in http://communities.vmware.com/docs/DOC-11113 This is the reason ESXi not licensed is not supported because it's not scriptable. Thanks
VMware ESX/ESXi License keys required to work with VDS Posted on March 22, 2011 by ian For VDS to be able to work with VMware ESX/ESXi it must use vCLI. This is the remote scripting environment to interact with the hosts. vCLI is available with one of the following licenses : vSphere Essentials vSphere Essential Plus vSphere Standard vSphere Advanced vSphere Enterprise vSphere Enterprise Plus. VDS will not work with the free license key called: vSphere Hypervisor This information was obtained from: http://kb.vmware.com/selfservice/micros ... 0157393663 License Information: VMware vSphere for Small Business: http://www.vmware.com/vmwarestore/vsphe ... tions.html NON SMB Licenses: https://www.vmware.com/vmwarestore/vsph ... tions.html
Note here : * - The free version of ESXi does not have support for vCLI thus the connection broker will not work. Thanks
