Comments on: vMotion – A general system error occurred https://magander.se/vmotion-a-general-system-error-occurred/ Thu, 26 Jan 2017 17:29:54 +0000 hourly 1 https://wordpress.org/?v=6.9.4 By: magander3 https://magander.se/vmotion-a-general-system-error-occurred/#comment-111215 Thu, 26 Jan 2017 17:28:23 +0000 http://magander.se/?p=6025#comment-111215 In reply to Joe Aiello.

Thanks for letting me know.

//Magnus

]]> By: Joe Aiello https://magander.se/vmotion-a-general-system-error-occurred/#comment-111203 Thu, 26 Jan 2017 16:02:56 +0000 http://magander.se/?p=6025#comment-111203 Still relevant upgrading my 5.5 to 6.0. Thanks.

]]> By: magander3 https://magander.se/vmotion-a-general-system-error-occurred/#comment-53928 Tue, 27 Oct 2015 08:27:42 +0000 http://magander.se/?p=6025#comment-53928 In reply to Lieven.

Hi, i’m not sure exactly what the setting mean but i can try to find out.

//Magnus

]]> By: Lieven https://magander.se/vmotion-a-general-system-error-occurred/#comment-53890 Tue, 27 Oct 2015 03:45:53 +0000 http://magander.se/?p=6025#comment-53890 I got the same issue (vCenter 5.5 build 2001466 and ESXi 5.5 build 2143827) and changing Migrate.VMotionResolveSwapType from 1 to 0 resolved the issue.

VMware did however not yet update KB 1031636 to include vSphere 5.5

What could be the possible downside of setting Migrate.VMotionResolveSwapType to 0? In oyther words, why would one not set this option by default to 0?

]]>