Part 1 – Getting Stared with HPE Morpheus VM Essential 9.1

Last week we covered Proxmox VE and the use of Ceph. HPE’s VME sits on the same KVM/QEMU/libvirt foundation, but its operating model is built to feel like vCenter. Both Proxmox and VM Essentials run on KVM/QEMU and are built similar

Proxmox VE is Debian based and HPE VM Essentials is Ubuntu based.

Morpheus Data was multi‑cloud orchestration and automation platform Hpe acquired so today this software acts as the automation and lifecycle management layer for Hpe.

With Morpheus integrated, HPE launched HPE Morpheus VM Essentials (VME), a virtualization solution that manages virtual machines running on HPE’s KVM-based HVM hypervisor. The VME manager deploys workloads and can even manage vCenter clouds from the same console, so it gives the easy migration we can do between private clouds.

HPE acquired Juniper Networks, and this got them Mist AI (cloud‑managed networking),Apstra (intent‑based data‑center automation) SDN capabilities and AI operations layer they were missing.

So today, HPE Morpheus VM Essentials allows us for easy deployment of KVM Based HVM workloads even into VMware vCenter all managed via HPE Morpheus VM Essentials Manager. 

LayerHPE product
Automation + lifecycleMorpheus
VirtualizationVME / HVM (KVM)
Networking + SDNJuniper Mist, Apstra
Consumption modelHPE GreenLake

Documentation

Together, these acquisitions form HPE’s modern private cloud stack and a strong VMware alternative.

The Morpheus Software Family

HPE now ships Morpheus as two products:

1. HPE Morpheus VM Essentials

This is hardware-agnostic and can be deployed quickly.

  • Manages KVM (HPE HVM hypervisor) – HVM OS 26.04, new in 9.1)
  • Manages VMware ESXi
  • Ideal for SMBs, labs, edge, and mid‑market
  • Licensed per socket, not per core
  • Includes a 60‑day free trial (up to 6 sockets)
  • The Manager is a Morpheus appliance deployed as a VM on the cluster

Each HVM host runs HVM OS, HPE’s Ubuntu-based host OS, with KVM/QEMU, libvirt and a VME agent the Manager talks to. Host networking is set by the cluster layout you pick when you create the cluster: on layout HVM 2.0 (HVM OS 26.04, new in 9.1) you build virtual switches in the Manager, while the older 1.3 and Legacy layouts use Open vSwitch bridges.

2. HPE Morpheus Enterprise (HPE Private Cloud Business Edition)

Think of this as it’s a bundle on the HPe’s own hardware

  • Full cloud management suite
  • Built for large enterprises and service providers
  • Supports hybrid cloud, public cloud, containers, governance, automation, and more

Why Morpheus Matters

The key advantage and the reason customers are paying attention is the socket-based licensing model.

With modern CPUs packing 32, 48, or 64 cores per socket, per‑core licensing (like VMware’s new model) becomes extremely expensive, so this makes VM Essentials a strong option for customers wanting multi hypervisor flexibility.

HPE then bundled VM Essentials into a full private cloud offering so the VME which is known as HPE Private Cloud Business Edition

Core Components of Hpe Morpheus

  • HVM hypervisor: the equivalent of ESXi
  • HVM cluster: the equivalent of an ESXi cluster
  • VME Manager: the equivalent of vCenter
  • Shared storage: GFS2 for FC/iSCSI LUNs (3+ hosts), NFSv3 (the 2-node option), Ceph for HCI

Comparison between VM Essentials and Morpheus Enterprise

VM EssentialsMorpheus Enterprise
ManagesHVM (KVM) clusters + VMware ESXi via vCenterMulti-hypervisor, public cloud, containers/Kubernetes, bare metal
Best fitSMB, mid-market, edgeLarge enterprises and service providers
Think of it asvSphere + vCenter replacementVCF Automation-style cloud management platform
LicensingPer socket, cores don’t count; 1, 3 or 5-year termsPer socket; upgrade SKUs from VME available
US list price$600 per socket per year incl. supportHigher and quote-based
Free optionEvaluation periodCommunity Edition for non-production home labs

Comparison between vSphere and VME

vSphereVME
ESXi hostHVM host
vCenter ServerVME Manager
vSphere clusterHVM cluster
VMFS datastore on a LUNGFS2 datastore
NFS datastoreNFS datastore
Local VMFSDirectory Pool
vSANCeph or SimpliVity
vSwitch / port groupOVS bridge domain / HVM network
vMotionLive migration
Storage vMotionMove disk to another datastore
vSphere HAHA
DRSWorkload balancing + placement rules
VM templates / Content LibraryVirtual images + Image Store
Host ProfilesHost Profiles
HCXBuilt-in VMware-to-HVM migration
vCenter backupManager backup
vSwitch backed by vmnic uplinksOVS Bridge Domain backed by bond
Port groupHVM Standard Network
VMkernelLinux Bond

Networking in VM Essentials

VME networking is Open vSwitch under the hood so think of this as standard switch in vSphere.

As with ESXi, the switch port is a trunk and the VLAN tag lives on the network object, not in the guest.. The networking on VM Essentials is pretty similar to Proxmox.

Storage in VM Essentials

VME uses GFS2, Red Hat’s clustered filesystem, for shared iSCSI/FC storage. GFS2 needs quorum, so it needs at least 3 hosts. With fewer hosts, use NFS (2 hosts) or a local Directory Pool (1 host). Ceph is the option for HCI.

In the next series, we are going to reuse the outer Proxmox host from last week, swap the three Proxmox nodes for three nested HVM hosts, and add us the same ISCI linux San we created last week for Proxmox..

(Visited 61 times, 1 visits today)

By Ash Thomas

Ash Thomas is a seasoned IT professional with extensive experience as a technical expert, complemented by a keen interest in blockchain technology.