I am having an issue with importing a VM on a MS Server 2008 R2 Core that is configured with an ISCSI SAN. I am trying to import a VM that came from a different server. I used the export feature within HyperV Manager to transfer the data. I am receiving the error that I cannot import due to lack of space during the import process. I noticed that HyperV is trying to import the VM to the local disk (~ 80GB ) of the new server. The export data of the VM (~140GB) resides on the SAN volume (~320GB). I have no troubles creating a new VM and placing the data of the VM on the SAN. I am having a hard time understanding why would HyperV Manager change the data location of the VM and not use the export location. I understand I can create a new VM and simply attached the VHD but I prefer not to go this route and lose the current configurations of the VM.
Keep Up with TechRepublic