Azure Migrate gives a cannot eject virtual DVD error

Chris Davis 45

Moc-operator cannot eject virtual DVD during migration to Azure local after fail over complete.

Karthick Ragavan v2 0 Reputation points

2025-01-09T12:27:15.5366667+00:00

moc-operator virtualmachine serviceClient returned an error while reconciling: rpc error: code = Unknown desc = Failed to cleanup seed iso disk from the file system for vm : Failed to cleanup seed iso disk from the file system for vm : ErrorCode[32768] ErrorDescription['VM' failed to remove device 'Microsoft:Hyper-V:Synthetic DVD Drive': %%2147749900 (0x8004100C). (Virtual machine ID )] ErrorSummaryDescription [Failed to remove device 'Microsoft:Hyper-V:Synthetic DVD Drive': %%2147749900 (0x8004100C).]: WMI Error 0x00008000","additionalInfo":[{"type":"ErrorInfo","info":{"category":"Uncategorized","recommendedAction":"","troubleshootingURL":""}}]}}', error message: 'moc-operator virtualmachine serviceClient returned an error while reconciling: rpc error: code = Unknown desc = Failed to cleanup seed iso disk from the file system for vm .: Failed to cleanup seed iso disk from the file system for vm .: ErrorCode[32768] ErrorDescription['VM' failed to remove device 'Microsoft:Hyper-V:Synthetic DVD Drive': %%2147749900 (0x8004100C). (Virtual machine ID )] ErrorSummaryDescription [Failed to remove device 'Microsoft:Hyper-V:Synthetic DVD Drive': %%2147749900 (0x8004100C).]: WMI Error 0x00008000 Status: 200 (OK) ErrorCode: Failed Service request succeeded. Response content and headers are not included to avoid logging sensitive data. '.
Chris Davis 45 Reputation points

2025-01-09T12:34:54.3366667+00:00

Yes.. that is the same error.
Karthick Ragavan v2 0 Reputation points

2025-01-09T12:46:41.67+00:00

Can you share the workaround
Karthick Ragavan v2 0 Reputation points

2025-01-09T12:47:14.7666667+00:00

Can you share the workaround
Chris Davis 45 Reputation points

2025-01-09T12:50:31.0466667+00:00

See above :)
Rahul Podila 1,070 Reputation points Microsoft Vendor

2025-01-10T02:31:50.0333333+00:00
Hi @Chris Davis

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

In the Azure portal, find your VM and check the settings. Look for the DVD drive and make sure it's not still attached. If it is, go ahead and set it to None or remove it.

Try turning off the VM, wait a few seconds, and then turn it back on. Sometimes this helps clear up issues after a migration.

If that doesn’t work, you can use a PowerShell command to remove the DVD drive. Here's an example of the command:

Get-AzVM -ResourceGroupName <YourResourceGroup> -Name <VMName> | Set-AzVM -RemoveDataDisk <DriveName>

Just replace <YourResourceGroup>, <VMName>, and <DriveName> with your actual details.

If you moved the VM from an on-premises Hyper-V server, double-check the settings there to make sure the DVD drive was removed before migrating to Azure.

Finally, if nothing else works, you may need to restart the migration process to make sure the DVD drive isn’t attached during the move.

If your any concern, please go through this link: -
https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/azure/manage-vm

If you have any further queries, do let us know.

3 answers

Lionel Ong 20 Reputation points

2025-01-05T23:05:45.7733333+00:00
Ensure the VM is fully powered on and operational after the failover.

Manually eject the virtual DVD from the VM settings in the Azure portal.

Verify the recovery point is complete and valid.

Check that you're using the latest version of the Azure Migrate tools and MOC operator.

Review migration settings to ensure the virtual DVD is not included.

Retry the migration after ejecting or detaching the virtual DVD.

Ensure no processes inside the VM are using the virtual DVD.

Check migration logs for any additional error details.
Please sign in to rate this answer.
Chris Davis 45 Reputation points

2025-01-06T10:51:24.23+00:00

Thanks Lionel. The problem is that the cleanup that occurs when the seed.iso virtual DVD removal fails as part of "preparing protected entities" see below - removes the migrated VM from the Azure Local cluster. So the VM is not powered up and the DVD cannot therefore be manually ejected.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jon McCabe 5 Reputation points MVP

2025-01-07T16:41:51.09+00:00

Is this a Gen1 or Gen2 Hyper-V VM? And what do you mean "removes migrated VM from the Azure Local cluster"? Are you saying the migration fails completely? Have you looked in both Failover Cluster Manager and Hyper-V Manager? I know there can be issues if the source VM is using the D:\ drive or has an ISO mounted because that is needed for the Arc seed.
Please sign in to rate this answer.
Chris Davis 45 Reputation points

2025-01-07T19:33:59.5066667+00:00

This is Gen1 Hyper-V VM, yes the migration fails completely. Even when the DVD is removed from Hyper-V prior to migration the same problem occurs. After the failed migration the VM does not appear in either the Azure Local FCM or Hyper-V Manager. I am running Solution version 10.2411.1.10

Jon McCabe 5 Reputation points MVP

2025-01-07T19:57:38.4366667+00:00

Make sure nothing else is configured to use the D:\ drive letter, that seems to be reserved for the CD-ROM. Check this article, specifically the SAN policy, as it might be relevant. Besides that, migrate a different VM to rule out the VM Migration Appliance or something else. Gen1 VMs require extra steps to Arc Enable but they should still migrate successfully.

Chris Davis 45 Reputation points

2025-01-08T14:56:28.9666667+00:00

Thanks - I have now had an update from Azure Local Product Support- which says We've seen a similar event with Configuring Guest Management for azure arc Vms, and the workaround involves prior mounting the moc,iso image. Its a generic error after all. it just means yes we lack the capability to mount or unmount a specific device. No fix atm.

Lionel Ong 20 Reputation points

2025-01-09T09:27:20.44+00:00

Thanks Chris, are you able to share the workaround steps here with us?

Karthick Ragavan v2 0 Reputation points

2025-01-09T12:27:34.9733333+00:00

Getting similar error during VMware VM migration to Azure Local, any suggestion

Chris Davis 45 Reputation points

2025-01-09T12:48:29.6566667+00:00

Yes.. the workaround is simply to wait until the migration gets this this stage (at which time the migrated VM should pop up in the Azure Local Failover Cluster Manager,) Then simply edit the VM settings in the FCM to eject the DVD. The migration then continues to successful conclusion. Timing is crucial, leave it too long and the migration will clean up, delete the VM and fail!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Jon McCabe 5 Reputation points MVP

2025-01-09T14:11:18.96+00:00

Not sure which workaround you are referring to, but to enable Guest Management on a Gen1 migrated VM you need to follow the steps outlined here:

Enable guest management for migrated VMs (preview)

Hope this helps.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Azure Migrate gives a cannot eject virtual DVD error

3 answers

Your answer