When you manage your Hyper-V environment with Turbonomic, our software manages resources to ensure that your VMs always get the resources they need to perform. Additionally, most customers will stitch their virtualization layer to other parts of the stack, including Applications and Databases, Container Platforms, Cloud for hybrid cloud management, Storage, Hyper-Converged, etc. Only Turbonomic provides this extensive visibility, understanding the relationships between applications and infrastructure. And only Turbonomic generates automatable actions that prevent performance degradation.
If you have a small number of Hyper-V hosts in your environment, you can add them individually as Turbonomic targets. Also, if you have deployed the Hyper-V hosts in a clustered domain (for example as a failover cluster), you can specify one Hyper-V host as a target and Turbonomic automatically add the other members of that cluster.
Note that for large Hyper-V environments, it’s typical to manage the hosts via System Center Virtual Machine Manager (VMM). You can specify the VMM server as a target and Turbonomic will use it to discover and manage its child Hyper-V hosts. If you use VMM, you should not add individual Hyper-V hosts as targets. For information about adding VMM targets, see Adding Virtual Machine Manager Targets.
- Virtual Machine
- Physical Machine
- VM Virtual Memory, CPU, Storage, IOPS, and Latency
- Physical Machine Memory, CPU, IO, Net, Swap
- Storage Amount, Provisioned, IOPs, Latency
- Data Center Memory, CPU, IO, Net, Swap
- For Virtual Machines: Start, Move, Suspend, Storage Move, Resize Down/Up, Terminate, Provision, Reconfigure
- For Physical Machines: Start, Suspend, Terminate, Provision
- For Storage: Provision