Michael Kuzmin

Oops, I'm dealing with the same bug in https://github.com/vmware/rbvmomi/pull/39. But it looks both our patches are wrong. Instead of changing `find_datacenter` method, or introducing `find_datacenter_working_edition` one, we'll probably have to...

Well, I think I've figured this issue out. This is not a bug, but a misconfiguration of our vCenter instances. VMware could design vCenter permission model better, and maybe its...

That would be cool!

I agree, we need to make SATA optional, and use IDE by default. The only reason using it was macOS - not a mainstream use case

even without SATA controller, a minimal config is still incompatible with version 9

@cfryanr I need your help here. If I set hardware version to 9, even for a minimal VM configuration, vSphere API returns an error: ``` The virtual machine version is...

My minimal gist above contains nothing special, and still reproduces the issue. I appreciate if you directly communicate this to [govmomi](https://github.com/vmware/govmomi) team or VMware support.

The error happens at VM creation moment. I'm pretty sure vCenter shows an event with details for that. I'd suggest two tests to localize the root cause: 1) Create VM...

Then start with a config with a minimal set of parameters, and add them one by one. ``` { "builders": [ { "type": "vsphere-iso", "vcenter_server": "vcenter.vsphere65.test", "username": "root", "password": "jetbrains",...

need to warn you in advance. `book_command` is not compatible with vSphere 6.0 (#63).