VMware Cloud Community
vlaghavarapu
Contributor
Contributor
Jump to solution

vMotion using PowerCli 6.5 release1 is failing with vSphere Web Client 6.7.0.1150 build 8170132

vMotion is failing when tried with PowerCli 6.5 release1. Below errors are observed:

PowerCLI C:\> Get-VM -Name rh75_vm | move-vm -Destination xx.xx.xx.xx

move-vm : 7/25/2018 11:49:11 AM Move-VM         Exception has been thrown by the target of an invocation.

At line:1 char:24

+ Get-VM -Name rh75_vm | move-vm -Destination xx.xx.xx.xx

+                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Move-VM], VimException

    + FullyQualifiedErrorId : Core_BaseCmdlet_UnknownError,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

* Destination IP address was replaced with xx

Manually tried vMotion from Web Client, it was working fine.

Can someone please help me how to resolve the issue. Please let me know whether PowerCli6.5 U1 is compatible with vSphere Web client 6.7.0.1150 build 8170132 ?

Thanks,

Vinay.

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

According to the interoperability matrix you need at least VMware PowerCLI 10.1.0.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

0 Kudos
2 Replies
LucD
Leadership
Leadership
Jump to solution

According to the interoperability matrix you need at least VMware PowerCLI 10.1.0.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
vlaghavarapu
Contributor
Contributor
Jump to solution

Thank you Luc. vMotion works after upgrading to PowerCli 10.1.0

Regards,

Vinay.

0 Kudos