VMware Workstation (vs) VMware ESX.?

automate

#1

VMware Workstation (vs) VMware ESX.?

I’m utilizing VMWARE Workstation 6.0 for recreation of tight bunches of “sharp edges” in a “frame”. Both the host and target OSs are Linux. Every “undercarriage” utilizes a vmnet switch as a virtual backplane, to which the virtual cutting edges associate. Other vmnet changes are utilized to intercede point-to-point associations between mutiple virtual ethernet connectors on every edge VM. The frame, and along these lines the VMs, are raised and shutdown rather much of the time. My contents (python) make substantial utilization of the VIX programming interface, and furthermore control the .vmx config record.

What do I pick up as well as lose going from VMware Workstation to ESX? Do my contents that utilization the VIX programming interface still work? Do my somewhat entangled virtual system topologies, with loads of vmnet switches characterized as “custom”, still work a similar way? Is the linguistic structure and semantics of the .vmx config record the same amongst Workstation and ESX?


#2

@agrare can you help here or know someone who might be able to help? It isn’t exactly a ManageIQ question.


#3

@emmablisa so going from workstation to a ESXi standalone host you go to a type 1 hypervisor which will give your guest VMs better performance compared to sharing resources with everything else your local workstation is doing.

You can still use VIX to connect to an ESX host but you can also use the much more full featured VIM/vSphere web services SDK (https://www.vmware.com/support/developer/vc-sdk/)

Probably the biggest benefit of moving to ESXi is that you can add a vCenter and add multiple hosts as your workload increases.

I would strongly recommend against any direct vmx file modifications, the “right way” is to use the ReconfigVM_Task method (https://code.vmware.com/apis/196/vsphere#/doc/vim.VirtualMachine.html#reconfigure).