VMware Cloud Community
Kimbie
Contributor
Contributor

Unable to move datastores with vmotion

We are trying to do a live migration of datastores of some of our VMs and it is failing with "A general system error occurred: Source detected that destination failed to resume" this happens around about 18% into the progress, it sits on 18% for approx 15 - 20 seconds before failing

We have HP 460c blades with 48Gb Ram and dual X5540s with an iSCSI mez card in each blade.

There is enough space on the new datastore, I have been able to move one of the VMs without any problem and that was a 2008R2x64 machine, the others we are trying to move are either 2008x64 or 2003EEx64.

To move the datastore, I am going into migrate, pick the data store and tell it to get on with it.

Any way I can get this to work? Without having to power down the VMs? Or mess with any of the advanced settings?

Cheers

Tags (3)
Reply
0 Kudos
5 Replies
RvdNieuwendijk
Leadership
Leadership

Maybe increasing the Storage VMotion fsr.maxSwitchoverSeconds setting in the virtual machine configuration file to a larger value will help. See: VMware Knowledge Base: Using Storage VMotion to migrate a virtual machine with many disks may timeou... for more information.

Regards, Robert

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
Reply
0 Kudos
Kimbie
Contributor
Contributor

The problem with that option is we need to power down the VMs to do the change. I also do not want to have to power down a VM to do the change every time

Kimbie

Reply
0 Kudos
RvdNieuwendijk
Leadership
Leadership

The Knowledge Base article also writes: "Alternatively, at the time of Storage VMotion Migration, avoid running a large number of provisioning operations, migrations, or power on/off operations on the same datastores the Storage VMotion migration is using."

Maybe that will help.

Blog: https://rvdnieuwendijk.com/ | Twitter: @rvdnieuwendijk | Author of: https://www.packtpub.com/virtualization-and-cloud/learning-powercli-second-edition
Reply
0 Kudos
Rajeev_S
Expert
Expert

Below thread looks promising

http://communities.vmware.com/message/1545132


Award Points if helpful!!

Reply
0 Kudos
tietzjd25
Enthusiast
Enthusiast

I have always fix this issue by rebooting the Vm's. Never dived off in to it too much, just felt that there was some kind of file lock on peice of the storage. Reboot the VM and then move worked, I also only seen this when I been making massive changes......

Joe Tietz VCAP-DCD Solutions Architect
Reply
0 Kudos