Running into a "small" issue when migrating VM's to a new hyper-v host image.
I had hyper-v running from a USB drive/stick. Due to issues with the network drivers I thought it would be best to start with a clean hyper-v image again. The server is now booting from this new image without any issues but I am unable to import the existing
VM's (they are in a saved state).
PS E:\> Import-VM -Path 'E:\shares\hyperv\sv-win-dc01\Virtual Machines\E148B999-7F6C-4464-B45D-A19170BF601F.xml'
Import-VM : Unable to import virtual machine due to configuration errors.
Please use Compare-VM to repair the virtual machine.
PS E:\> $report.Incompatibilities | Format-List
Message : Virtual Hard Disk file not found.
MessageId : 40010
Source : Microsoft.HyperV.PowerShell.HardDiskDrive
Message : Virtual Hard Disk file not found.
MessageId : 40010
Source : Microsoft.HyperV.PowerShell.HardDiskDrive
PS E:\> $report.Incompatibilities[0].Source | Format-List
DiskNumber :
SupportPersistentReservations : False
MaximumIOPS : 0
MinimumIOPS : 0
ControllerType : SCSI
ControllerNumber : 0
ControllerLocation : 3
Name : Hard Drive on SCSI controller number 0 at location 3
PoolName : Primordial
Path : E:\shares\hyperv\sv-win-dc01\Virtual Hard Disks\sv-win-dc01_data.vhdx
Disk :
ComputerName : SV-WIN-HYPER01
Id : Microsoft:E148B999-7F6C-4464-B45D-A19170BF601F\E6B4069B-005B-442D-A63A-2D5DCD9DF13D\0\3\D
IsDeleted : False
VMId : e148b999-7f6c-4464-b45d-a19170bf601f
VMName : sv-win-dc01
VMSnapshotId : 00000000-0000-0000-0000-000000000000
VMSnapshotName :
Key :
PS E:\> $report.Incompatibilities[1].Source | Format-List
DiskNumber :
SupportPersistentReservations : False
MaximumIOPS : 0
MinimumIOPS : 0
ControllerType : SCSI
ControllerNumber : 0
ControllerLocation : 4
Name : Hard Drive on SCSI controller number 0 at location 4
PoolName : Primordial
Path : E:\shares\hyperv\sv-win-dc01\Virtual Hard Disks\sv-win-dc01_backup.vhdx
Disk :
ComputerName : SV-WIN-HYPER01
Id : Microsoft:E148B999-7F6C-4464-B45D-A19170BF601F\E6B4069B-005B-442D-A63A-2D5DCD9DF13D\0\4\D
IsDeleted : False
VMId : e148b999-7f6c-4464-b45d-a19170bf601f
VMName : sv-win-dc01
VMSnapshotId : 00000000-0000-0000-0000-000000000000
VMSnapshotName :
Key :
The VM config file (xml) contain the correct path's to these vhdx files:
<drive3>
<iops_limit type="integer">0</iops_limit>
<iops_reservation type="integer">0</iops_reservation>
<pathname type="string">F:\shares\hyperv\sv-win-dc01\virtual hard disks\sv-win-dc01_data.vhdx</pathname>
<persistent_reservations_supported type="bool">False</persistent_reservations_supported>
<type type="string">VHD</type>
<weight type="integer">100</weight>
</drive3>
<drive4>
<iops_limit type="integer">0</iops_limit>
<iops_reservation type="integer">0</iops_reservation>
<pathname type="string">g:\shares\hyperv\sv-win-dc01\Virtual Hard Disks\sv-win-dc01_backup.vhdx</pathname>
<persistent_reservations_supported type="bool">False</persistent_reservations_supported>
<type type="string">VHD</type>
<weight type="integer">100</weight>
</drive4>
Please note that the vhdx files were NOT moved during the hyper-v image migration. So does anyone have any idea why Import-VM is incorrectly expecting these vhdx files to be residing on drive E:\ ?
Thank you in advance.