Please provide your feedback in this short Flings' survey.
Mar 23, 2020

For some reason I can download the vGPU and PDF instructions.

Mar 23, 2020

Sorry, the URLs have been fixed. I'm about to release v1.0.1. If you can give me 30min, you'll get the latest version :)

Mar 23, 2020

Hi! I want to use a ESXi 5.5 server that I have laying around but as I can see, the requirements are at least for ESXi 6.0. Is any way I can change that? When I try to deploy the .ova file it says "Unsupported element "property".

Mar 23, 2020

The initial requirements is actually vCenter Server and 6.5+ :)

Having said that, we've relaxed it and I'm about to release v1.0.1 in next 30min. In addition, ESXi Host Client has issues and if you only have standalone ESXi host, you'll need to use OVFTool. Please see the deployment instructions for how to do that. I'd also recommend waiting for 1.0.1 which uses vHW 11 (there are no plans to reduce that any further as vHW == 6.0)

Mar 23, 2020

I'm attempting to use Windows PowerShell to import the 1.0.1 VM. My host is the Esxi 6.0 Free license. Is this Esxi version too old or does the free license restrict me at all? I also got "Line 159: Unsupported element 'Property'" when attempting to use the web interface.

I'm getting the following error:
The manifest validates
Opening VI target: vi://root@192.168.xx.xx:443/
Error: OVF Package is not supported by target:
- Line 159: Unsupported element 'Property'
Completed with errors

Mar 25, 2020

Same issue using ovftool on Mac on ESXi standalone (6.0.0 Update 3 (Build 8934903)) licence VMware vSphere 6 Enterprise Plus

Mar 22, 2020

Unable to login as root. I tried setting a root password during the initial import, however, I'm unable to login as root.

Mar 22, 2020

Did you deploy the OVA to vCenter Server?

Mar 23, 2020

Did you copy paste the root password during deployment or type it in. I had same issue and now redeployed using a password I typed in. works now.

Mar 22, 2020

I got the problem, that it is mostly failed to get a connection:

failed o ge assignment from"65.254.110.245:8080" (80) empty work server assignment

ANY idea ??

Mar 22, 2020

It just means there aren't any WU's being assigned and you'll need to wait. Everything is configured correctly. From what I hear, only Large WU's are available which require FaH Clients to have >= 16 vCPUs. If you have such resources and you configure it, you should get a WU. To do so, just shutdown the VM and update the VM's configuration and power it back on, everything will be auto-detected.

Mar 23, 2020

Does this mean I should only deploy 16vCPU machines? Can I use multiple vGPUs with a single VM? Is this rule still valid when doing vGPU folding?

Mar 23, 2020

You can deploy using any vCPU configuration you're comfortable with, if you can spare 16+, then you're more likely to receive WU. In terms of multiple vGPU, I'm not 100% sure but we do have documentation using NVIDIA GRID