If the vmotion occurs between two nodes of a cluster where the resource pool resides it will automatically default to that resource pool - however if you vmotion between to ESX servers not part of a cluster you will be asked which resource pool to place the VM into -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

Interesting I thought it defaulted to the resource pool - but you do have the option to select the resource pool when doing a manual vmotion do you not?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

also think this is the most irritating failure of vCenter... you always have to check where the vm belongs to, if you do a migrate

I'd like to second this feature request.  Any migration (vmotion, svmotion, offline migrate) should by default maintain the same resource pool.  But more than simply defaulting to the current pool, there should be an explicit option for "maintain current resource pool", so that it is possible to migrate multiple VMs from different resource pools simultaneously. 

For example: in the case of a SAN upgrade a user could have hundreds of VMs to move... Only the datastore needs to be changed - the host and resource pools should stay the same.  I want to select a list of VMs and issue one SVMotion command.  Instead I have to create a list of VMs I want to move, go to the Hosts and Clusters view and find each one individually (in order to determine its current resource pool), manually migrate that VM, and move on to the next.  For just one of my clusters, what could be 5 or 6 clicks turns into 2000-3000 clicks.

Yes, this has got to get fixed.  The ability to change resource pools should stay, but it should be in an "advanced" button/screen out of the way because it will rarely get used.

In the mean time, drag and drop VMs to perform the VMotioning and it asks less questions.

Jas

[i]Jason Boche, VCDX #34, VCPx3, vExpert[/i]

[boche.net - VMware Virtualization Evangelist|http://www.boche.net/blog/][/i]

[VMware Communities User Moderator|http://www.vmware.com/communities/content/community_terms/][/i]

[Minneapolis Area VMware User Group Leader|http://communities.vmware.com/community/vmug/us-central/minneapolis][/i]

[vCalendar|http://www.boche.net/blog/index.php/vcalendar/] Author[/i]

Yeah but your still SOL when it comes to a storage VMotion I concur this needs to get fixed....PLEASE

I might have the solution to this problem. I have created a script which enables you to VMotion and SVMotion VMs without having to specify the resource pools. The VMs will automatically be put into their respective resource pools after the migration. The script actually generates a GUI and it contains features like host-to-host migration, vm-to-host migration, datastore-to-datastore migration, vm-to-datastore migration and the Undo feature. Have a look at:

http://easymigration.blogspot.com/2010/09/easy-migration-script-for-vmware-using.html

This script will save you heaps of time when you have to manually VMotion or SVMotion VMs. Let me know guys what you think about my script.

This is a great feature request. I hate having to double click on a VM just to see which Resource Pool it resides on so that I can choose it too in the Migration Wizard.

If this post has been helpful/solved your issue, please mark the thread and award points as you see fit. Thanks!

Strange that this is not fixed yet. Should be easy to fix.

It's driving me nuts.

That script may work, in my opinion it shouldn't be nessesary to use script to achive this.

I totally agree with this. It is a simple thing that would save so much time. I am surprised to see that this goes back to 2009 and has not yet been adressed.

Still an issue in 2017 so far as I can tell.

Hi Eric,

Thanks for bringing this to our attention.  Consider this added to our backlog, so we have it on our radar as we're building out the new vSphere Client (HTML5).