- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cannot migrate powered on VM
On vSphere v7.0.3 I'm having an issue with migrating a powered on VM from one host to another, when its suspended it will migrate over fine. Other VM's migrate when powered on.
On vSphere I get an event error immediately after initiating the migration: (VM Name and IP addresses have been removed)
- The virtual machine did not migrate. This condition can occur if vMotion IPs are not configured, the source and destination hosts are not accessible, and so on. Action: Check the reason in the event message to find the cause of the failure. Ensure that the vMotion IPs are configured on source and destination hosts, the hosts are accessible, and so on.
| 05/20/2022, 4:13:19 PM | Hot migrating VM_NAME from 10.***.**.**, EMC_Datastore1 in Broadcast DC to 10.***.**.**, EMC_Datastore1 in Broadcast DC with encryption |
| 05/20/2022, 4:13:19 PM | Task: Relocate virtual machine |
In the hostd.log I get this error:
2022-05-20T05:50:00.546Z info hostd[1050994] [Originator@6876 sub=Vcsvc.VMotionSrc.8655175433452394658 opID=l3cgeqc2-6445-auto-4z2-h5:70003116-1b-01-01-a3-3c41] ResolveCb: Failed with fault: (vim.fault.GenericVmConfigFault) {
--> faultMessage = (vmodl.LocalizableMessage) [
--> (vmodl.LocalizableMessage) {
--> key = "msg.vigor.operationCancelled",
--> message = "The operation was cancelled by the user.",
--> }
--> ],
--> reason = "The operation was cancelled by the user.",
--> msg = "The operation was cancelled by the user.
--> "
--> }
In the vpxa.log I get this error:
2022-05-20T06:13:19.918Z info vpxa[1052518] [Originator@6876 sub=Default opID=l3cgeqc2-9929-auto-7nu-h5:70005470-cf-01-75] [VpxLRO] -- ERROR lro-23427 -- vmotionManager -- vim.host.VMotionManager.initiateDestination: vmodl.fault.SystemError:
--> Result:
--> (vmodl.fault.SystemError) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> reason = "Invalid fault"
--> msg = "Received SOAP response fault from [<<io_obj p:0x0000000d3757cb58, h:24, <TCP '127.0.0.1 : 61211'>, <TCP '127.0.0.1 : 8307'>>, /sdk>]: initiateDestination
--> vim.fault.GenericVmConfigFault"
--> }
--> Args:
-->
--> Arg migrationId:
--> 8655175434851822558
--> Arg dstConfigPath:
--> "ds:///vmfs/volumes/627b6499-0de5c79b-e216-0892049f83c4/VM_NAME/VM_NAME.vmx"
If anyone is able to assist resolve this issue it would be much appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi;
Verify that the VM does not have enabled Encrypted vMotion.
Enable or Disable Encrypted vMotion
vSphere vMotion always uses encryption when migrating encrypted virtual machines. For virtual machines that are not encrypted, you can select one of the encrypted vSphere vMotion options.
I Hope that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is this a new cluster? Have you been able to move this vm before? Can you vmotion other vms? What’s the EVC mode and is the vm encrypted?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you set some policy on the VM that cannot comply with the migration (storage policy or encryption).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content