Sluggish performance on VMs migrated from Hyper-V
-
Statitica It's because of a change in Windows storage driver. Deleting
HKLM\SYSTEM\CurrentControlSet\Services\stornvme\StartOverridebefore booting on the new template should make it work. -
dinhngtu do I just do that before powering the VM down, or is there a way to do it on the disk while it is detached and powered down?
-
Statitica You can do that before powering down. There's XenBootFix, which isn't really made for this, but may also work.
-
dinhngtu stornvme doesn't have a StartOverride section.
Assume it is storahci?
-
Statitica If you're using the Windows templates, then stornvme is correct. Do you have some unusual NVMe drivers (Intel drivers being one) installed?
-
dinhngtu I originally used the "other install media" template when I imported this VM from hyper-v.
Nothing listed in msinfo, but in the reg keys under storahci
I noticed there are also drivers in there from vmware (these VMs have been through a few hypervisors before I took over the company and decided to do this particular migration).
Out of interest I checked a Server25 install which was done using the "Windows Server 2022" template. That also has no StartOverride value in the registry.
-
Statitica have you checked the Event Logs, specifically the System event logs? I recall having a performance hit when I migrated some VMs from Hyper-V to XCP-ng (years ago at this point).
I don't recall the exact issue off hand, but the remedy was easy enough.
-
DustinB There isn't anything in the eventlogs since the VSS/ESENT issue was cleared.
-
Statitica Not having
stornvme\StartOverrideis expected on systems that use NVMe controllers to boot (e.g. XCP-ng Windows templates). Can your imported VM boot on the correct Windows template once you have made surestornvme\StartOverrideis not present? Once it boots with the correct template and NVMe controller then let's see what the performances are. -
dinhngtu it still wouldn't boot with the correct template.
That said, I have been testing other VMs which were created on xcp-ng, with the correct templates, and get better performance out of them when they are migrated to a hyper-v host.
I believe that this is related to SMAPIv1 limitations - which are known and being actively worked on with SMAPIv3.Unfortunately for us at this point, xcp-ng may not fit our business - hopefully one day soon it will be, but until then, it is what it is.