Two new bundles:
* hvm_qualification_matrix (sd00006551en_us) — the "Qualification Matrix
for HVM Clusters Managed by HPE Morpheus Software". Single TOC bundle,
2 pages (parent + content). The content page is ~100 KB of HTML
containing five tables: Server Hardware Support, Storage Hardware
Support, Independent Software Vendor (ISV) Support, Hypervisor OS
Compatibility and Interoperability Matrix, and Guest OS. Scraped via
the same /hpesc/public/api/document/{docId}/render endpoint as every
other bundle on support.hpe.com — the API returns server-rendered
DITA HTML, so no JS/SPA shenanigans.
* hvm_quickspecs (a50004260enw) — HPE Morpheus VM Essentials Software
QuickSpecs, Version 4 (02-Feb-2026). SKUs: S5Q81AAE (1-yr per Socket
E-LTU), S5Q82AAE (3-yr), S5Q83AAE (5-yr); each includes Tech Care
Essentials. QuickSpecs lives at www.hpe.com (not support.hpe.com),
which drops connections at the edge for non-browser TLS fingerprints —
verified 2026-05-22 against curl, wget, urllib, and Anthropic's
WebFetch (all = 0 bytes / connection timeout in headers). Bypassed
here via curl_cffi impersonating Chrome 120's JA3/JA4 fingerprint.
HTTP 200, 255 KB on first try, all four sections + all three SKUs
cleanly parseable from the server-rendered HTML.
New module scrape/quickspecs.py drives the live fetch + parse for any
hvm_*_quickspecs bundle. CSS selectors taken from the captured DOM:
.lr-right-rail hpe-highlights-container .collateral-content
— one block per H3 section
h3.txto-title — section title
div.txto-description — section body
uc-table.uc-table-polaris — SKU and version-history tables
On any live failure the parser falls back to a committed HTML fixture
at scrape/quickspecs/<doc_id>.html so the build never breaks on a
transient edge hiccup.
scrape/runner.py learned a new mode "html-file" that dispatches to
scrape.quickspecs; bundles.py extended with an optional source_url on
BundleSpec for cases where the page lives outside support.hpe.com.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
# Qualification Matrix for HVM Clusters Managed By HPE Morpheus Software
This document contains the list of hardware and software that has been tested and confirmed to support HVM Clusters managed by HPE Morpheus Software at scale. **Items not included in this list may be compatible but are untested.** Using untested hardware or software may limit the scope of support services available from HPE support teams.
New hardware and software are continually being tested and certified. This document will be updated over time as new hardware SKUs are confirmed compatible and performant at scale.
NOTE
There is a self-validation program for partners to quickly validate their solutions for compatibility with HVM. For more information about the program, see [the self-validation program documentation](https://www.hpe.com/psnow/doc/a00155725enw?jumpid=in_pdfviewer-psnow).
Table 1. Server Hardware Support
| Hardware Family | Platform Type | Hardware SKU | Comments |
1 For Synergy hardware device support, review the latest SSP published for Ubuntu at <https://support.hpe.com/docs/display/public/synergy-sw-release/OS_Support.html>. Please note that HPE Synergy D3940 is not supported, and for additional information on Ubuntu support in HPE Synergy, refer to the [Customer Notice a00129603](https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-a00129603en_us).
Table 2. Storage Hardware Support
| Vendor | Hardware Family | Platform Type | Comments |
1 Applications have been validated within the bounds of the supported HPE Morpheus Software functionality. Always check the HPE Morpheus Software feature list to determine whether specific functionality is supported by the HVM hypervisor (ex. shared disk access).
2 Protection of NFS and GFS2 datastores
3 For the manual pool use case where desktop lifecycle is not managed and instant clones are not applicable. Improved user experience, increased user density, and cost efficiency with vGPU support in future HPE Morpheus VM Essentials releases.
4 SimpliVity and HPE Morpheus Software do not yet support Veeam image-based and agent-based backups
Most modern applications like databases were designed with very “loose” dependance on hardware infrastructure. They can typically run on a variety of hypervisors including virtual machines and containers. The respective ISV vendor typically only specifies the supported underlying operating system (Guest OS) but does not require certification of any hypervisor. However, there can be specific features that a customer deployment of these applications requires at a hypervisor or infrastructure level. For example, a Microsoft SQL Server Failover cluster instance requires a shared disk between multiple SQL Server VMs. Oracle, similarly, requires shared disks for an Oracle Real Application Cluster (RAC) setup. Therefore, it needs to be always validated whether the specific deployment requires certain features and whether these are supported by VM Essentials in its latest release.
Select ISV applications require “full stack” certifications including OS, hypervisor, compute and storage devices, or even the specific storage connectivity protocol. SAP HANA and related SAP applications are a typical example; so are some Healthcare Electronic Health Record (EDR) applications. If you or your customer plans on running one of these applications, please reach out to your HPE account team.
Table 4. Hypervisor OS Compatibility and Interoperability Matrix
| OS Vendor | OS Family | Compute Platform | Storage Platform |
| --- | --- | --- | --- |
| Canonical | Ubuntu 22.04 Server, 24.04 Server | x86 | Alletra; iSCSI |
Table 5. Guest OS
| Partner | Product Name | Product Version | Validation Type | Resources |
| --- | --- | --- | --- | --- |
| RHEL | RHEL | 8, 9, 10 | HPE | |
| CentOS | CentOS | 8 | HPE | |
| SUSE | SUSE Linux Enterprise Server | 15‐SP4, 15‐SP6 | HPE | |
| Microsoft | Windows Server | 2016, 2019, 2022, 2025 | HPE | |
- [OS Support Matrix](https://www.hpe.com/us/en/collaterals/collateral.a50010841enw.html)
- [HPE Support Center for VME](https://www.hpe.com/support/VME-Docs)
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
