topic Re: Automated Driver Injection in HPE Morpheus VM Essentials Software

Automated Driver Injection

dya — Sat, 27 Jun 2026 21:57:00 GMT

Has anyone else experienced the same issue with Automated Driver Injection?

My understanding is that the VirtIO drivers must be installed automatically before the migration starts. However, I have encountered cases where the migration proceeded to the data transfer phase without the VirtIO drivers being installed first, and the migrated VM ultimately failed to boot at the destination.

In that particular migration plan, both Windows Server 2016 and Windows Server 2022 were included.

For this reason, I believe the most reliable approach is to run virtio-win-guest-tools.exe before starting the migration. What do you think?

https://support.hpe.com/hpesc/public/docDisplay?docId=sd00008058en_us&page=GUID-3A8E263B-7508-4620-A5C6-5372D385F0DB.html#ariaid-title1

Re: Automated Driver Injection

sahilanand7 — Tue, 07 Jul 2026 16:03:48 GMT

Thats correct for windows it better to run virtio-win-guest-tools.exe before kicking of migrations.

Re: Automated Driver Injection

DiegoDelgado — Tue, 07 Jul 2026 16:39:59 GMT

You can see the process in the Morpheus log. I've seen some cases where it fails because WinRM is not enabled or doesn't allow connections.

A workaround would be to temporarily change the RPC mode in the VMW cloud to VMware Tools before migrations, I've seen this work pretty consistently.

Re: Automated Driver Injection

dya — Wed, 08 Jul 2026 08:16:53 GMT

It sounds like this is related to VMware Cloud's RPC mode.

One thing that concerns me is that the migration proceeds to the data transfer phase even if the pre-installation fails. I think it would be better to perform the prerequisite step first and only proceed to the next stage if everything succeeds. If there's a problem, it would be detected immediately at that point.

Given that, I'm still torn about whether it might be a good option to simply run virtio-win-guest-tools.exe manually before starting the migration. It's probably the most reliable approach and adds very little overhead to the migration process.