justin/hvm-docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
41d431670fbb454b1d83b58e00f87db72cee9cc3
hvm-docs/corpus/hvm_deployment_guide/GUID-94742592-9C85-4F2E-83F2-E68404A73F3B.md
T
hvm-docs-refresh 8743fff510 weekly refresh: 2026-05-22T17:39Z — 1161 content change(s) across 7 bundle(s) 
1161 content change(s) across 7 bundle(s)
1161 sidecar metadata update(s)
7 new bundle(s) added

Bundles with content changes:
  hvm_deployment_guide (NEW): 32 page(s)
    - GUID-0F55384D-5632-4CDC-AA39-A21C1C089AFA
    - GUID-28F18596-4902-4CD1-83F3-1411430C5534
    - GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259
    - GUID-34B1D00A-C42E-4691-8B4F-3B110E34FE7C
    - GUID-3DA92E9D-0635-427A-BA9D-5A7E475B55DB
    ... and 27 more
  hvm_release_notes_8_1_0 (NEW): 1 page(s)
    - sd00007497en_us
  hvm_release_notes_8_1_1 (NEW): 1 page(s)
    - sd00007609en_us
  hvm_release_notes_8_1_2 (NEW): 1 page(s)
    - sd00007734en_us
  hvm_user_manual_8_1_0 (NEW): 374 page(s)
    - GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
    - GUID-02679208-A796-4A58-80AC-33DCF6A4899F
    - GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
    - GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
    - GUID-0503F050-177F-4360-9B1A-49439AF366B8
    ... and 369 more
  hvm_user_manual_8_1_1 (NEW): 376 page(s)
    - GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
    - GUID-02679208-A796-4A58-80AC-33DCF6A4899F
    - GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
    - GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
    - GUID-0503F050-177F-4360-9B1A-49439AF366B8
    ... and 371 more
  hvm_user_manual_8_1_2 (NEW): 376 page(s)
    - GUID-008AF6CD-E219-4D76-B175-B763E5C397CE
    - GUID-02679208-A796-4A58-80AC-33DCF6A4899F
    - GUID-034C2E21-6B14-4AAD-A582-2638A4C7D04C
    - GUID-04410F73-1BA6-46D4-A7A4-E4706C5FD522
    - GUID-0503F050-177F-4360-9B1A-49439AF366B8
    ... and 371 more
2026-05-22 17:39:22 +00:00

4.5 KiB
Raw Blame History

Upgrade process

Having copied over the needed files and connected to the VM Essentials manager VM, the upgrade is completed in just a few commands. These commands will stop the current services, install the package, and then reconfigure the Manager. Replace the placeholder .deb file in the commands below with the correct path and file name of the package you’ve copied over.

IMPORTANT

Upgrading VM Essentials manager will result in downtime of 10-15 minutes. Ensure users are not doing critical work during the upgrade window. This downtime applies only to the Manager itself and has no effect on the hypervisor host(s) or any provisioned VMs currently running.

sudo morpheus-ctl stop morpheus-ui
sudo dpkg -i xxxx.deb
sudo dpkg -i xxxx.supplemental.deb # Optional -- Only for offline upgrades
sudo morpheus-ctl reconfigure

All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the UI service to watch UI startup logs with morpheus-ctl tail morpheus-ui. Once the UI service is up and running, the upgrade process is complete. Attempt to reach your appliance normally through a web browser to confirm success.

NOTE

  • Services will be stopped during package installation and started during the reconfigure process, including the morpheus-ui service.
  • If the reconfigure process is interrupted or fails, the morpheus-ui service may need to be manually started or restarted.
  • In certain situations if another service hangs on starting during reconfigure, run systemctl restart morpheus-runsvdir then reconfigure and restart morpheus-ui if successful.

Following upgrade, it's advisable to check for any available HVM Host Agent upgrades. To upgrade the HVM Host Agent, navigate to an HVM Host detail page, expand the ACTIONS menu, and click "Upgrade Agent." This process must be repeated for each HVM Host that makes up the HVM Cluster.

Alternatively, you could also select "Download Agent Script" to download an Agent upgrade script which can be run when connected to the host through a terminal session. The Agent upgrade scripts are Host-specific so an individual script would need to be downloaded for each HVM Host.

Upgrade sequence procedure

This section contains a table of compatible upgrade paths. The far left column contains the HPE Morpheus VM Essentials Manager version you're starting from. The columns to the right indicate versions compatible for upgrade from your starting version. If the version number is listed, it is a compatible upgrade path. If an "X" is listed instead, the upgrade path is unsupported.

NOTE

It is possible to span multiple versions in a single upgrade. For example, you can upgrade directly from HPE Morpheus VM Essentials version 8.0.3 to version 8.0.6, or from version 8.0.7 to version 8.0.11, and so on. Consult the table below for compatible or incompatible version upgrade hops.

From Version To Version
8.0.1 → 8.0.2 8.0.3 8.0.4 8.0.5 8.0.6 8.0.7 8.0.8 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.2 → 8.0.3 8.0.4 8.0.5 8.0.6 8.0.7 8.0.8 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.3 → 8.0.4 8.0.5 8.0.6 8.0.7 8.0.8 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.4 → 8.0.5 8.0.6 8.0.7 8.0.8 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.5 → 8.0.6 8.0.7 8.0.8 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.6 → 8.0.7 8.0.8 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.7 → 8.0.8 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.8 → 8.0.9 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.9 → 8.0.10 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.10 → 8.0.11 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.11 → 8.0.12 8.0.13 8.1.0 8.1.1 8.1.2
8.0.12 → 8.0.13 8.1.0 8.1.1 8.1.2
8.0.13 → 8.1.0 8.1.1 8.1.2
8.1.0 → 8.1.1 8.1.2
8.1.1 → 8.1.2
Reference in New Issue View Git Blame Copy Permalink