Quantcast
Channel: Hyper-V forum
Viewing all articles
Browse latest Browse all 8743

Can't import VM exported from another machine

$
0
0

I have 2 servers both running Windows Server 2012 R2. One server is currently running a Hyper-V instance. I have configured the running machine and checked the option under Processor > Compatibility, "Migrate to a physical computer with a different processor version". I shut the VM down, then exported it. After copying it to the new machine I've attempted to import it. I select the folder where I copied the files to and it recognizes the VM. I select "Register the virtual machine in-place". Then it prompts to select where the virtual hard disks are located. I pick the same folder I picked when adding the VM. As soon as I hit next, I get this message:

[Window Title]
Saved State Errors

[Main Instruction]
The following saved state errors were reported:
The processor settings for virtual machine 'PROD1VM - (4/15/2016 - 8:44:17 PM)' are not compatible with physical computer 'BACKUP'. To migrate this virtual machine, you must first shut it down. After shutdown, you can migrate this virtual machine or export it and then import it on the destination physical computer with the correct processor settings. (Virtual machine ID 21424D5E-BB09-4564-83B3-5DDD5C518482)
 The operation cannot proceed unless these errors are resolved.  Do you want to delete the save states producing these errors in order to continue?

[Delete Saved State] [Cancel]

The thing is, I HAVE done that. Multiple times. If I click "Delete Saved State", it then prompts me to select where the "C" drive for the VM is, the D drive, then the AVHDX file for the C drive, then finally the AVHDX for the D drive. After selecting those, it fails with this:

[Window Title]
Import Wizard

[Main Instruction]
Hyper-V encountered an error during the import operation.

[Content]
'PROD1VM' could not be realized due to validation errors.

[Expanded Information]
'PROD1VM' could not be realized due to errors in its configuration file which could not be resolved. (Virtual machine ID 2E4F0668-17BC-4F53-82B6-4BBDB2FFD81D)

[^] Hide details  [Close]

I'm not sure what else to try. Each time I retry this export/import cycle it takes the better part of a day to export the stopped VM (which takes a few hours), then another few hours to copy it to the other server/datacenter. If it matters, the total VM size is somewhere around 350GB.

Any ideas on what is causing this to fail?


Viewing all articles
Browse latest Browse all 8743

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>