Replies posted by Garet
There are some instances where this can occur if the migration of the VM was completed and then Move was upgraded prior to completing the cutover, or if the source VM has a disconnected NIC, but these issues largely only affect Move versions 3.X. Accordingly, please ensure that you are using a recent version of Move and, if not, you might consider upgrading to the latest available then retrying the cutover to find if the issue is still exhibited.
You may want to confirm the version of the VirtIO driver being used on the Windows Server 2022 machines. Currently, version 1.1.7 of the VirtIO driver package contains the drivers for Windows Server 2022. If you find that you are using version 1.1.6 or earlier, you might consider upgrading them to version 1.1.7 to see if the issue is resolved after that. You can download version 1.1.7 of the VirtIO driver package from the Downloads section of the Portal, as per the following link.
Thank you for providing this detailed analysis and information (and for submitting it to the void :) ). Indeed, you are correct in this behavior and our developers have already identified, created and resolved a defect according to this specific issue. Currently and, though always subject to change, the resolution should be included within the 6.1 and later release versions.
When creating a new virtual machine through the Prism Web UI, there should not be an option for disk provisioning type as it defaults to thin-provisioned. Accordingly, could you attempt to create the VM using the Prism Web UI, as per the instructions from the following linked documentation, and confirm if the resulting disk is still reported as thick-provisioned? Creating a VM (ESXi)
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.