jeremym wrote:
Then, before I tried to even MAKE my next pool...
...
3. Ran the diagnostics. I have a small and large version (with process dumps).
PS: I mentioned it earlier, but just to be on the safe side.. I'm implementing the WHOLE THING inside VMware Workstation as a proof of concept lab. All of it. The DC, vConnect, vCenter, ESXi, VMware Client.. Everything. http://screencast.com/t/pidQbTneRd7
Ok, first off the support bundle won't be of much use when you ran it as the VM is not yet configured for a pool. It therefore won't have a set of servers to try and connect to and test.
Secondly, nested inside workstation may well be your issue here. Nesting _may_ be ok if everything is set up correctly, but it also might be interfering with the ability for the desktop VM to get its configuration from the (virtual) ESX host. I assume you've set the monitor_control.restrict_backdoor = TRUE flag on your virtual ESX VMs? You're definitely well into unsupported territory but if you can get software inside the windows VM to read the machine.id field from the vmx file then everything should work (don't expect any kind of usable performance though!). You can test this by using tools: vmtoolsd --cmd "machine.id.get".