Home / server / Questions / 925664
Accepted
InteXX
Asked: 2018-08-10 07:32:26 +0800 CST

Error: Migration operation failed. The operation is not supported

  • 772

In Hyper-V 2016, I'm getting an error "Operation not supported" when attempting to move my VM configurations from a USB drive to the default folders. I have only one host machine; I exported them to the drive so I could perform some hardware upgrades that necessitated an OS reinstall. (The new disk array is still building, so I'll forego moving the VHDXs for now. The configurations are working, but I'd like to get them off the USB drive.)

The options I'm choosing are detailed in the screenshots below.

Things I've tried:

  1. Shutting down the VM (An Ubuntu Server instance)
  2. Moving just the main configuration, leaving out Checkpoints and Smart Paging
  3. Running the migration in PowerShell

PowerShell:

$Path = "C:\ProgramData\Microsoft\Windows\Hyper-V"
Move-VM -Name "MATRIX" -DestinationHost "SERVER1" -VirtualMachinePath $Path -SnapshotFilePath $Path -SmartPagingFilePath $Path

This fails with the same error:

The operation is not supported.

How can I successfully move these configurations to their default locations on the Hyper-V host?

enter image description here enter image description here enter image description here enter image description here enter image description here enter image description here enter image description here enter image description here enter image description here enter image description here

hyper-v

1 Answers

  1. Best Answer

    The error was occurring because I was trying to migrate a VM from one location to another on the same host. This action isn't supported—the concept of VM migration implies two separate hosts. (But not storage migration; this can be done within the same host without any problem. I suppose that's what left me thinking that I could do the same for configurations.)

    I ended up doing this for each VM:

    1. Create a new configuration with a slightly different name
    2. Manually copy the settings from the old configuration to the new
    3. Delete the old configuration
    4. Rename the new configuration

    This worked just fine.

    Frustration: If the error message had stated the true problem, it would have saved us all a lot of trouble. In literally a second I would have decided to approach the task in the way I've described, had I known what was really happening. I learned during my investigations that Hyper-V is infamous for this error reporting shortcoming. Somebody somewhere took some ill-advised shortcuts.

    • 0