weekly refresh: 2026-07-13T06:01Z — 7 content change(s) across 1 bundle(s)
7 content change(s) across 1 bundle(s)
0 sidecar metadata update(s)
1 other file change(s)
Bundles with content changes:
hvm_deployment_guide: 7 page(s)
- GUID-2DD9D39D-9031-4BB5-A4ED-A0179BEF5259
- GUID-456E190C-E912-4079-A691-8D2368D63748
- GUID-5FC0010C-8D7C-4A32-B84B-6CBC29041DCB
- GUID-88494051-74D1-4BD9-BAFF-134A573FF77B
- GUID-94742592-9C85-4F2E-83F2-E68404A73F3B
... and 2 more
This commit is contained in:
hvm-docs-refresh
+1
-1
@@ -113,7 +113,7 @@
|
|||||||
"mode": "toc",
|
"mode": "toc",
|
||||||
"abstract": "HPE Morpheus VM Essentials Deployment Guide",
|
"abstract": "HPE Morpheus VM Essentials Deployment Guide",
|
||||||
"dates": {
|
"dates": {
|
||||||
"Published": "January 2026"
|
"Published": "July 2026"
|
||||||
},
|
},
|
||||||
"landing_page": "GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099",
|
"landing_page": "GUID-BF94B8DA-C4F6-4CDF-99E6-0AAA03177099",
|
||||||
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us"
|
"source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007332en_us"
|
||||||
|
|||||||
@@ -4,13 +4,13 @@ This is where management and VM traffic is converged over the same bonded interf
|
|||||||
|
|
||||||
In an ideal scenario, you would have at least four network interfaces spread across at least two network cards on the host (shown in green on the diagram below). Ideally you would also have two separate network switches to help ensure resiliency and redundancy. As mentioned in the prior section, these networking examples are all created with resiliency and redundancy in mind. One storage lane is connected to each switch and likewise one management/VM lane is connected to each switch, which are bonded in and active/backup configuration. Consult the bonding table in the prior section for more details on the benefits and drawbacks to different types of network bonds.
|
In an ideal scenario, you would have at least four network interfaces spread across at least two network cards on the host (shown in green on the diagram below). Ideally you would also have two separate network switches to help ensure resiliency and redundancy. As mentioned in the prior section, these networking examples are all created with resiliency and redundancy in mind. One storage lane is connected to each switch and likewise one management/VM lane is connected to each switch, which are bonded in and active/backup configuration. Consult the bonding table in the prior section for more details on the benefits and drawbacks to different types of network bonds.
|
||||||
|
|
||||||
**Example 1**
|
## Example 1
|
||||||
|
|
||||||
In this scenario, the bond handles management/VM traffic failover while multipathing handles storage failover. A diagram of such a network setup is shown below:
|
In this scenario, the bond handles management/VM traffic failover while multipathing handles storage failover. A diagram of such a network setup is shown below:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Example 2**
|
## Example 2
|
||||||
|
|
||||||
In the example below, we have native VLAN on the trunk ports and on the storage ports. This means the network switch is tagging all the traffic for you and you don't have to tag it yourself. This allows you to put your IP addresses directly on the interfaces and bonds. Here, the storage VLANS get their own IP address directly on the interface while the management IP address goes directly on the bond as shown in the diagram below. With this configuration, all can be done in the installation wizard as long as the VLANs are piped to the interfaces as expected from the network switches. More specific guidance on using the installation wizard is included in later sections covering the software installation.
|
In the example below, we have native VLAN on the trunk ports and on the storage ports. This means the network switch is tagging all the traffic for you and you don't have to tag it yourself. This allows you to put your IP addresses directly on the interfaces and bonds. Here, the storage VLANS get their own IP address directly on the interface while the management IP address goes directly on the bond as shown in the diagram below. With this configuration, all can be done in the installation wizard as long as the VLANs are piped to the interfaces as expected from the network switches. More specific guidance on using the installation wizard is included in later sections covering the software installation.
|
||||||
|
|
||||||
@@ -24,7 +24,7 @@ Below is a chart showing the connection from the bonded network interfaces creat
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Example 3**
|
## Example 3
|
||||||
|
|
||||||
The prior example included native VLANs on the trunk ports and storage ports so we'll now take a look at an example configuration without native VLANs. You need to create VLAN tags on the interfaces because the switch is no longer handling the tagging for you. Your IP addresses then go on those VLAN tags. In this example bond0 becomes the compute interface and bond0.x becomes the management interface when configuring the cluster in a later step (see [Creating an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html)). When not using a native VLAN, the storage VLANs still get their own IP address and interface but a VLAN interface gets created on the bond and the management IP address goes on the VLAN interface.
|
The prior example included native VLANs on the trunk ports and storage ports so we'll now take a look at an example configuration without native VLANs. You need to create VLAN tags on the interfaces because the switch is no longer handling the tagging for you. Your IP addresses then go on those VLAN tags. In this example bond0 becomes the compute interface and bond0.x becomes the management interface when configuring the cluster in a later step (see [Creating an HVM cluster](https://support.hpe.com/hpesc/public/api/document/sd00007332en_us/render?page=GUID-99397996-8315-49C1-9E2F-2EED51CE03F3.html)). When not using a native VLAN, the storage VLANs still get their own IP address and interface but a VLAN interface gets created on the bond and the management IP address goes on the VLAN interface.
|
||||||
|
|
||||||
@@ -34,8 +34,8 @@ Just as in the similar chart above, the chart below shows the connection from th
|
|||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Example 4**
|
## Example 4
|
||||||
|
|
||||||
The same networking setup can be used with an LACP bond, however this does require extra configuration on the network switch side. The exact setup steps would depend on the specific hardware in your environment. The network setup would look something like the example below:
|
You can use this same networking setup with an LACP bond, but this requires extra configuration on the network switch side. Specifically, you must bond the physical switches into a single logical switch so the MLAG can form. The specific hardware in your environment will dictate the exact setup steps. The network setup would look something like the example below:
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
@@ -33,7 +33,7 @@ With VM Essentials manager up and running, you can now access the UI front end b
|
|||||||
5. Enter your license and select **Complete Setup**. If you don’t have a valid license or are just evaluating the solution, a 30 day evaluation period is activated by default.
|
5. Enter your license and select **Complete Setup**. If you don’t have a valid license or are just evaluating the solution, a 30 day evaluation period is activated by default.
|
||||||
|
|
||||||
- The main Appliance Setting screen opens with several configuration options. The next steps focus on the main items you’ll need to configure to create your first cluster.
|
- The main Appliance Setting screen opens with several configuration options. The next steps focus on the main items you’ll need to configure to create your first cluster.
|
||||||
- You need a pre-existing Group and Cloud to add your first HVM cluster. Groups define logical groupings of resources and users access those resources based on the Groups associated with their Roles. A Cloud can represent a grouping of HVM clusters or a connection into a VMware vCenter environment. You can read more on [Groups](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007230en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html) and [Clouds](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007230en_us&docLocale=en_US&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html) in the HPE Morpheus VM Essentials Software Documentation. This guide will go through the process of adding Private Cloud-type Clouds which house HVM clusters. For VMware-type Clouds, see the associated [integration guide](https://hpevm-docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware.html).
|
- You need a pre-existing Group and Cloud to add your first HVM cluster. Groups define logical groupings of resources and users access those resources based on the Groups associated with their Roles. A Cloud can represent a grouping of HVM clusters or a connection into a VMware vCenter environment. You can read more on [Groups](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008058en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html) and [Clouds](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008058en_us&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html) in the HPE Morpheus VM Essentials Software Documentation. This guide will go through the process of adding Private Cloud-type Clouds which house HVM clusters. For VMware-type Clouds, see the associated [integration guide](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008058en_us&page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html).
|
||||||
6. Create the first group.
|
6. Create the first group.
|
||||||
1. Go to Infrastructure > Groups on the top menu.
|
1. Go to Infrastructure > Groups on the top menu.
|
||||||
|
|
||||||
|
|||||||
@@ -2,4 +2,4 @@
|
|||||||
|
|
||||||
Provides further information on configuration and workflows.
|
Provides further information on configuration and workflows.
|
||||||
|
|
||||||
For further information about HPE Morpheus VM Essentials configurations and management, see [HPE Morpheus VM Essentials Software Documentation](https://www.hpe.com/support/morpheus-vm-essentials-documentation-latest)
|
For further information about HPE Morpheus VM Essentials configurations and management, see [HPE Morpheus VM Essentials Software Documentation](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008058en_us).
|
||||||
|
|||||||
@@ -1,5 +1,5 @@
|
|||||||
# API reference
|
# API reference
|
||||||
|
|
||||||
Contains the full API reference for interacting programmatically with HPE Morpheus VM Essentials.
|
Contains the API reference for interacting programmatically with HPE Morpheus VM Essentials.
|
||||||
|
|
||||||
See the HPE Morpheus VM Essentials [API reference](https://apidocs.morpheusdata.com/docs/getting_started) for a complete endpoint list and example call formation.
|
See the HPE Morpheus VM Essentials [API reference](https://apidocs.morpheusdata.com/docs/getting_started) for a complete endpoint list and example call formation.
|
||||||
|
|||||||
@@ -35,20 +35,21 @@ 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.
|
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 | | | | | | | | | | | | | | |
|
| 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.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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 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 | 9.0.0 |
|
||||||
| 8.0.13 → | | | | | | | | | | | | | 8.1.0 | 8.1.1 | 8.1.2 |
|
| 8.0.13 → | | | | | | | | | | | | | 8.1.0 | 8.1.1 | 8.1.2 | 9.0.0 |
|
||||||
| 8.1.0 → | | | | | | | | | | | | | | 8.1.1 | 8.1.2 |
|
| 8.1.0 → | | | | | | | | | | | | | | 8.1.1 | 8.1.2 | 9.0.0 |
|
||||||
| 8.1.1 → | | | | | | | | | | | | | | | 8.1.2 |
|
| 8.1.1 → | | | | | | | | | | | | | | | 8.1.2 | 9.0.0 |
|
||||||
|
| 8.1.2 → | | | | | | | | | | | | | | | | 9.0.0 |
|
||||||
|
|||||||
@@ -1,5 +1,5 @@
|
|||||||
# Qualification Matrix
|
# Qualification Matrix
|
||||||
|
|
||||||
Contains the list of hardware and software that has been tested for compatibility with HPE Morpheus VM Essentials Software.
|
Contains the list of hardware and software tested for compatibility with HPE Morpheus VM Essentials Software.
|
||||||
|
|
||||||
Hardware and software is continually being tested and certified for compatibility with HPE Morpheus VM Essentials Software. For full details, see [The Qualification Matrix for HPE Morpheus VM Essentials Software](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006551en_us&page=GUID-EA7C0803-E66B-4B17-B994-30D4025A258F.html). Items not listed in that document may be compatible but are untested.
|
Hardware and software is continually being tested and certified for compatibility with HPE Morpheus VM Essentials Software. For full details, see [The Qualification Matrix for HPE Morpheus VM Essentials Software](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006551en_us&page=GUID-EA7C0803-E66B-4B17-B994-30D4025A258F.html). Items not listed in the qualification matrix document may be compatible but are untested.
|
||||||
|
|||||||
@@ -2,51 +2,64 @@
|
|||||||
|
|
||||||
This section will go through the steps to prepare a Windows image for deployment on HVM clusters. This image can serve as a template from which additional images and VM Essentials Library items can be built. This section only discusses the Virtual Image configuration fields needed to be successful with this example Windows deployment. For more generalized information on Virtual Images, including configurations needed for successful Linux deployment, see the **Library** **>** **Virtual Images** of the product user manual.
|
This section will go through the steps to prepare a Windows image for deployment on HVM clusters. This image can serve as a template from which additional images and VM Essentials Library items can be built. This section only discusses the Virtual Image configuration fields needed to be successful with this example Windows deployment. For more generalized information on Virtual Images, including configurations needed for successful Linux deployment, see the **Library** **>** **Virtual Images** of the product user manual.
|
||||||
|
|
||||||
1. In this example case, we’ll start from downloading a Windows Server ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in VM Essentials that users can provision on-demand.
|
In this example case, we’ll start from downloading a Windows Server ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in VM Essentials that users can provision on-demand.
|
||||||
2. With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in VM Essentials. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
|
|
||||||
- **NAME:** A name for the Virtual Image in VM Essentials, such as “Windows Server 2025 ISO”
|
|
||||||
- **OPERATING SYSTEM:** “Windows Server 2025”
|
|
||||||
- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
|
|
||||||
3. In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
|
|
||||||
4. With the configurations set, it’s time to upload the ISO to VM Essentials. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space in your VME Manager appliance to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large drop zone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled **Add File** and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal.
|
|
||||||
|
|
||||||
|
With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in VM Essentials. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
|
||||||
5. After the file has completely uploaded, click SAVE CHANGES. Rather than dropping and uploading the file through this modal, users may also select the URL/PATH radio button. This results in a URL field replacing the file drop zone where a URL to external storage containing the image may be entered.
|
|
||||||
|
|
||||||
NOTE
|
- **NAME:** A name for the Virtual Image in VM Essentials, such as “Windows Server 2026 ISO”
|
||||||
|
- **OPERATING SYSTEM:** “Windows Server 2026”
|
||||||
|
- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
|
||||||
|
|
||||||
Alternatively, you can source the file from an integrated bucket (if any currently exist) by selecting the bucket in the BUCKET field and entering a path to the image in the URL field. When uploading the image via URL or path, the Virtual Image can be saved and closed as soon as all configurations are finished. Image upload will continue in the background. When uploading via file drop, the modal must remain open until the upload process is completed.
|
In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
|
||||||
6. Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
|
|
||||||
7. On the GROUP tab, select the Group and Cloud containing the target MVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
|
|
||||||
8. On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration).
|
|
||||||
9. Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
|
|
||||||
10. As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
|
|
||||||
|
|
||||||
|
With the configurations set, it’s time to upload the ISO to VM Essentials. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space in your VME Manager appliance to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large drop zone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled **Add File** and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal. After the file has completely uploaded, click SAVE CHANGES. Rather than dropping and uploading the file through this modal, users may also select the URL/PATH radio button. This results in a URL field replacing the file drop zone where a URL to external storage containing the image may be entered. Alternatively, you can source the file from an integrated bucket (if any currently exist) by selecting the bucket in the BUCKET field and entering a path to the image in the URL field. When uploading the image via URL or path, the Virtual Image can be saved and closed as soon as all configurations are finished. Image upload will continue in the background. When uploading via file drop, the modal must remain open until the upload process is completed.
|
||||||
11. The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
|
|
||||||
12. Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
|
|
||||||
13. Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then **Open Console**. This will open a new window with a console session into the VM.
|
|
||||||
|
|
||||||
|
|
||||||
14. After selecting the language, click **Next**. On the following screen, click **Install Now**. This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click **Next**.
|
|
||||||
|
|
||||||
|
Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
|
||||||
15. Accept the licensing terms and click **Next**.
|
|
||||||
|
|
||||||
|
On the GROUP tab, select the Group and Cloud containing the target MVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
|
||||||
16. On the next screen, choose a custom install.
|
|
||||||
|
|
||||||
|
On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration). Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
|
||||||
17. The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
|
|
||||||
|
|
||||||
|
As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
|
||||||
18. After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
|
|
||||||
|
|
||||||
|
|
||||||
19. Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
|
|
||||||
|
|
||||||
|
The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
|
||||||
20. Step through the installer. Simply click **Next** or **Install** through each step, there are no configuration changes needed. Once the installer has completed, click **Finish**. You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
|
|
||||||
|
|
||||||
|
Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
|
||||||
21. We can now eject the two virtual disks, drives D: and E: in my case.
|
|
||||||
|
Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then **Open Console**. This will open a new window with a console session into the VM.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
After selecting the language, click **Next**. On the following screen, click **Install Now**. This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click **Next**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Accept the licensing terms and click **Next**.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
On the next screen, choose a custom install.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Step through the installer. Simply click **Next** or **Install** through each step, there are no configuration changes needed. Once the installer has completed, click **Finish**. You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
We can now eject the two virtual disks, drives D: and E: in my case.
|
||||||
|
|||||||
Reference in New Issue
Block a user