Cant Storage VMotion

[KGoch]

I am trying to do a Storage vMotion on a 3.0 ESX host and recieve this message: Unable to migrate from <source host> to <dest host>: With

current configurations, Vmotion between the specified hosts would

require a location change for the virtual machine swapfile, but this is

not supported on the source host <source host>.

I did not set this environment up that the host resides in so I have no idea where the swapfile settings are. I would love to change them so that I can Storage vMotion these VMs. ANy help is greatly appreciated!

[danpalacios]

Here are a couple of posts/links which may help you understand the requirements for storage vmotion

http://communities.vmware.com/thread/157602

http://communities.vmware.com/thread/121684

(You didn't mention which update you were on, so here is the list of admin guides)

Are you trying the storage vmotion using CLI or a VC plug-in? We have had instances in our 3.5 environment when a vm would not storage vmotion. When I asked the question of a VMware support tech, he mentioned that he had seen times when it was flakey through the plug-in and suggested we try to do it via the CLI. Haven't bothered with that test yet as we are prepping for 4.0

[TomHowarth]

ESX 3.0.0 does not have the functionality of svMotion this feature was only introducted with 3.5.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts

[KGoch]

Thanks guys. However i was able to Storage vMotion to go successfully once I powered off all the VMs. Go Figure.

[KGoch]

And it was ESX 3.0.0 Build 27701

[TomHowarth]

Cold Storage migration was always there with 3.0.0 but as you found out your VMs have to be powered off.

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert

VMware Communities User Moderator

Blog: www.planetvm.net

Contributing author for the upcoming book "[VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment|http://my.safaribooksonline.com/9780136083214]”. Currently available on roughcuts