First, you’ll have to decide what “manage” means. However you define that will determine how you feel about VMware’s Multi-Hypervisor Manager (MHM). If it’s “can I manage to access all VMs from another hypervisor and have a pretty good chance of converting them?” then you’re in luck. During the installation, VMware asks if you want to use their Stand-Alone Converter, which gives you a hint of the real reason behind MHM: Conversion.
If you’re looking for a way to change the number of live migrations that can be done at one time on a Hyper-V host, or anything that has to do with environment changes, then this plug-in will look a bit generic and unnecessary.
MHM is as much a manager as Michael Scott is. Sure, he’ll make a sale now and then, but mostly he’s just taking care of his own stuff and watching everything else. MHM can mess around some with the VM configuration and turn things on and off and create machines. It’s much more “type in the path if you know it off the top of your head” than browsing to sections or scrolling through available options during the creation process. After browsing around this VMware plug-in, I’m sure I would actually manage the alternate hypervisor via its own interface.
Let’s get to it then-
Finding the Install File
This wasn’t as easy as I had hoped. You’ll be better off searching for it via the All Downloads section in My VMware (search for ‘multi-hypervisor’). Licensed organizations will find it in the Open Source section of their vSphere Suite. Download both the server and client versions.
Installing On vCenter Server
– – Prepare by creating a user that has “Log On as a Service” right on the vCenter Server
– – Run the installer with the “Run As…” option as the Elevated Admin is needed. If you don’t, there will be some directory creation errors. The installation will finish (unfortunately) but it will fail upon execution inside the vSphere client.
– – In the vSphere client, open the Plug-in Manager. Right click to add a new plug-in.
Accessing the MHM
You’ll find the MHM in the Inventory section of the vSphere client. Click it to open the MHM in a separate window than the rest of your inventory (so much for the single pane of glass idea). You’ll get an immediate error if you used your AD credentials to login to the vSphere client (as I did).
Fix this by logging into the client with the local administrator account. Access the MHM and click the Permissions tab. Add your AD groups as you would for vCenter.
At this point you can change the service logon account. I changed mine back to Local System from a domain user.
No Web GUI Access
I didn’t see the MHM in VMware’s Web GUI. This is kind of a big deal since at the Denver VMUG I attended this week VMware was adamant that the vSphere client would be gone with the release of vSphere 6 (to be released in a year from now?)
Some examples of what is accessible after connecting a Hyper-V host:
Not much to do here, just look at. This is a good plug-in for accessing and converting everything to VMware, just not much else.