Windows Server 2022 cannot be installed on HPE VM Essentials

[dya]

I can't install Windows Server 2022 on HPE VM Essentials
I tried to install Windows Server 2022.

I loaded VirtIO, but it said that no new device drivers were found

I can't install it. What should I do?

*This is a machine translation. Sorry if it's hard to understand.

[ranjithpk174]

Please follow:

HPE VM Clusters — Morpheus Docs documentation

Also check the virtio drivers is available in the KVM hosts under /var/morpheus/kvm/images/virtio-win.iso.

Make sure you checked "Attach Virtio Drivers" from the Advanced option while provisioning the VM.

[dya]

Thank you.

I can find "Red Hat VirtIO SCSI Controller" on the Windows Server installation screen, but a message like "No new drivers found" appears and I can't proceed any further.

I can't find /var/morpheus/kvm/images/virtio-win.iso,
but virtio-win.iso is in the area where the GFS shared storage (iscsi) is mounted.

I'm stuck.

[dya]

I'm not sure what the cause is, but the installation of Windows Server 2022 has progressed. So far, it's going well.

I was also grateful that you provided me with the URL for the documentation.

Thank you very much.

[dya]

I was able to install it once, but I was also doing other testing so I reverted to a snapshot.

After reverting, I was unable to install Windows Server 2022 again.

When it was working fine, after I clicked "Install now", I wasn't suddenly told that the driver could not be found, but now I am told that.

[dya]

You can now install it by unchecking the image target on the shared storage (GFS2) editing screen in the cluster storage (datastore).

The provisioned VM directory looks like this:

# ls -hl /mnt/d6f86f9c-da75-48ce-94f0-8997b85900b5/windows2022/
Total 4.9G
-rw-r--r-- 1 root kvm 194K Mar 1 09:47 hpevm_47-disk-0
-rw-r--r-- 1 root kvm 4.9G Mar 1 09:47 hpevm_47-disk-1
#

The one I noticed was "hpevm_47-disk-1". This is the same size as the installer. When the image target was checked, it was about 1.7G.

How do I decide whether to check or not check an image target? Should I not check a GFS2 datastore? Should I check an NFS?

[DiegoDelgado · Accepted solution]

Hi,

let me expand on this... 

When you create an instance, the image from the library gets copied somewhere that is "close to the host" and then it gets deployed cloning the disk to the desired datastore. Where this image is cached depends on wheter the Image Target checkbox is selected or not.

If the Image Target checkbox is NOT selected in the datastore, the image will get copied to the server where the instance will be deployed and THEN the virtual disk will be created in the desired datastore. This will happen just once per host, meaning that if you deploy an instance of the same image to a different server it will get copied to that second server too.

If the Image Target IS selected in the datastore, tha image will get staged in the datastore and this will just happen once, whenever a new instance of the same image is deployed, the cluster will just copy the image from there.

I hope this is clear, but please follow up if you have any questions.

[AmitBiswas]

You need to get the virtio drivers in there, please look for the procedure here:
https://hpevm-docs.morpheusdata.com/en/latest/infrastructure/clusters/clusters.html#id1

[dya]

thank you.