We could verify the VM's existence, but had to do so using VMware's Virtual Infrastructure Client view (the front end to VMware's VirtualCenter management server), but it oddly did not have the same settings that we chose upon creating it with the TotalView tool.

We reinstalled the software, which seemed to help matters, and after adding the ESX VirtualCenter host to the TotalView system, we could then successfully execute commands like Clone, Stop and Start although other commands like Migrate and Clone To Template were grayed out in the application and therefore unusable.

Moves-adds-changes

After creating VMS, we weren't allowed to migrate them as that option was grayed out in the options box. We could do this manually -- outside of TotalView, with VMware's tools on VMware and using Citrix XenServer tools.

When we tried to snapshot a VM with TotalView, it seemed like it took the snapshot (we used the VMware Infrastructure client to verify that), but reverting back to the snapshot that was taken, then showed only a black screen and did nothing else. TotalView snapshots did not include the option to save the VM's memory contents (an option that in VMware's client is checked by default), therefore if you take a snapshot of a live VM and then revert while the VM is on, corruption could happen, as we indeed witnessed.