Share via

Export and Import virtual machines have identical configurations, including device IDs, serial numbers, and UUIDs.

Anonymous
2024-01-18T20:56:01+00:00

Hello

I recently encountered an issue with Export and Import virtual machines have identical configurations, including device IDs, serial numbers, and UUIDs in Hyper-V and would like to share my experience and seek advice from the community. Here's a summary of the situation:

Problem Statement:

  • I exported a Debian host VM from one Hyper-V and successfully imported it as a new Debian host VM.
  • During export, I selected the option to create a new unique ID.

Issue:

  • Both VMs have identical configurations, including device IDs, serial numbers, and UUIDs.
  • Attempting to run both VMs simultaneously results in an error: The power could not be turned on. The hypervisor could not complete the operation because the error 'object or value is already in use or for the purpose of not allowing the operation to be completed.

Steps Taken So Far:

  1. I just check about Sysprep tool. Sysprep is used to clone an existing Windows installation across multiple PCs. Sysprep generalizes Windows by removing the security identifiers and other computer-specific information.
  2. As the original VM is Linux-based, I couldn't use the Sysprep tool.
  3. Attempted to manually update the UUID using the dmisetuuid tool but encountered permission issues.

Are there specific steps or considerations I might be missing in the export/import process?

VM1 Debian Host: (Original Exported VM)

  • Serial Number: 7062-3961-6236-9675-1851-4697-14
  • UUID: df579c0e-214a-4826-9d47-d6b42d604880
  • MAC : 00:15:5d:1e:1d:19

VM2 Debian Host: (Original Exported VM)

  • Serial Number: 7062-3961-6236-9675-1851-4697-14
  • UUID: df579c0e-214a-4826-9d47-d6b42d604880
  • MAC : 00:15:5d:1e:1d:15

Request for Assistance:

If anyone has insights, recommendations, or potential solutions to resolve this duplicate VM conflict issue, I would greatly appreciate your guidance. Your expertise and experiences will be invaluable in addressing this challenge.

Thank you in advance for your time and assistance!

Best regards,

Samadhan

Windows for business Windows Server Storage high availability Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-19T02:39:30+00:00

    Hi Samadhan,

    Hope you're doing well.

    It seems that the issue you are facing is due to the identical UUIDs of the two VMs. The error message you received indicates that the hypervisor is unable to differentiate between the two VMs.

    One solution to this problem is to change the UUID of one of the VMs. You can do this by following the steps below:

    1. Shut down the VM that you want to change the UUID for.
    2. Open the Virtual Machine Connection window.
    3. Click on the "Edit Disk" option.
    4. Select the disk that you want to change the UUID for.
    5. Click on the "Modify" button.
    6. Enter a new UUID in the "New UUID" field.
    7. Click on the "Apply" button.
    8. Start the VM.

    If you are still encountering permission issues while attempting to update the UUID using the "dmisetuuid" tool, you may need to run the tool as an administrator.

    Here are the relevant documents for you reference:

    Changing or keeping a UUID for a moved virtual machine (1541) (vmware.com)

    virtualbox - Trying to open a VM config which has the same UUID as an existing virtual machine - Super User

    I hope this helps! Let me know if you have any further questions.

    Best Regards

    0 comments