MVM Cloud¶

Overview¶

MVM (Morpheus Virtual Machine) Cloud, also known as HVM (HPE Virtual Machine), is HPE Morpheus Software’s native KVM-based hypervisor platform. Unlike MVM Clusters which are managed via Infrastructure > Clusters, the MVM Cloud integration provides a cloud-level abstraction for provisioning and managing KVM virtual machines across distributed hypervisor hosts.

The MVM Cloud integration uses the kvmContainerService for provisioning and MvmHostService for host management.

Features¶

• KVM virtual machine provisioning and lifecycle management

• Virtual image management with template-based provisioning

• Host hypervisor management

• Network configuration (bridges, VLANs, OVS)

• Storage profile management

• Auto-scaling support

• Brownfield VM import

• Console access

Prerequisites¶

• One or more Linux hosts with KVM/QEMU installed and configured

• HPE Morpheus Software Agent installed on hypervisor hosts (or ability to install)

• Network connectivity between HPE Morpheus Software and hypervisor hosts

• Sufficient CPU, memory, and storage resources for VM provisioning

• Libvirt service running on target hosts

Adding an MVM Cloud¶

1. Navigate to Infrastructure > Clouds

2. Select + ADD

3. Choose MVM (or HVM) from the cloud type list

4. Configure:

   NAME

   Friendly name for the cloud

   CODE

   Unique code identifier

   LOCATION

   Optional location descriptor

   VISIBILITY

   Public (all tenants) or Private (master tenant only)

   TENANT

   Owning tenant for the cloud

5. Select NEXT and configure Group assignment

6. Complete the wizard

After adding the cloud, hypervisor hosts must be added to provide compute capacity.

Adding Hypervisor Hosts¶

1. Navigate to the MVM Cloud detail page

2. Select the Hosts tab

3. Click + ADD

4. Configure the host connection:

   SSH HOST

   IP address or hostname of the KVM hypervisor

   SSH USERNAME

   User with sudo privileges

   SSH PASSWORD / KEY

   Authentication credentials

5. HPE Morpheus Software will connect, install the agent, and begin managing the host

Instance Types¶

MVM Cloud supports two Instance Types:

• KVM (code: kvm) — Standard KVM virtual machine

• HVM (code: mvm) — High-performance virtual machine optimized for the Morpheus HVM hypervisor

Both use the same underlying kvmContainerService for provisioning.

Virtual Images¶

MVM/HVM provisioning supports QCOW2 and RAW Virtual Images. A multi-disk QCOW2 image requires one QCOW2 file per disk and a file named metadata.json on the same Virtual Image. The manifest maps filenames to disk capacities, guest device names, ordering, and the boot disk. Upload the QCOW2 files before the manifest.

See Multi-Disk QCOW2 Images for HVM/KVM for the manifest schema and upload procedure.

Provisioning¶

To provision a VM on MVM Cloud:

1. Navigate to Provisioning > Instances

2. Select + ADD

3. Choose the KVM or HVM Instance Type

4. Select the MVM Cloud as the target

5. Configure:

   IMAGE

   Select from available virtual images (typeahead from synced images)

   PLAN

   Select a service plan (CPU, RAM, storage configuration)

   NETWORK

   Select the target network (bridge, VLAN)

   HOST

   Optionally pin to a specific hypervisor host

   VOLUMES

   Configure disk(s) — size, type, datastore

6. Complete the wizard

Storage Profiles¶

MVM Cloud supports storage profiles that define storage characteristics:

• Storage backend type

• Performance tier

• Replication settings

• Volume type defaults

Storage profiles are configured via seed data and can be customized for specific environments.

Networking¶

MVM Cloud networking supports:

• Linux bridges — Standard Linux bridge interfaces

• Open vSwitch (OVS) — SDN-capable virtual switching

• VLANs — VLAN tagging on bridge/OVS ports

• Direct/passthrough — SR-IOV and PCI passthrough for high-performance networking

MVM Cloud vs MVM Cluster¶

Troubleshooting¶

• Host not connecting: Verify SSH connectivity and that the user has sudo access. Check that libvirt is running on the host.

• No images available: Ensure virtual images have been uploaded or synced. Images must be in a KVM-compatible format (QCOW2, RAW).

• Only one disk or missing data disks: Confirm the multi-disk QCOW2 image includes a valid metadata.json file and that each manifest filename matches an uploaded QCOW2 file.

• Wrong disk size or boot disk: Confirm capacities are expressed in bytes, disk positions are unique, and the intended root disk has boot set to true.

• Provisioning fails: Check available capacity on the target host. Verify storage pools have free space.

• Network errors: Confirm bridge interfaces exist on the hypervisor host and match the configured network names.

• Console not working: Ensure VNC/SPICE ports (5900+) are accessible from the HPE Morpheus Software appliance to the hypervisor host.