Quantcast
Channel: VMware Communities : Discussion List - VMware vCloud Director
Viewing all articles
Browse latest Browse all 4515

Migrating a VM to another ressource pool fails : Hub "Resources" doesn't meet compute requirement:

$
0
0

Hello

 

I have an issue when trying to migrate a VM to another ressource pool

 

     -within vCD 8.20 I have 2 ressource pools, both associated to the same Provider VDC. those 2 ressource pools are related, within vCenter, to 2 separate clusters : "SOURCE" and "DEST"

 

     -all hosts from both clusters are connected to the same DVS switch.

 

     -One host of "DEST" has an FC adapter trough which he is able to see all datastores from the SOURCE cluster. (( The reason of doing so is because DEST will be using vSAN in the future, so that host will be our "bridge" between the legacy FC storage and vSAN : once a VM is going to be vMotioned to it, we will update it's storage policy to vSAN thus triggering a storage vMotion))

 

     -EVC is enabled in "sandy bridge" mode on both clusters.

 

     -a vMotion of a VM initiated from vsphere web client between "SOURCE" and "DEST" works perfectly fine.

 

     -All VM's are located in the ressource pool "SOURCE". The goal is to migrate them to "DEST".

 

     -from vCD when I try to migrate a VM to my ressource pool "DEST", I am granted with the following error :

 

               [ 30836e4b-f761-438d-b263-9aecd5878a0d ] The operation failed because no suitable resource was found.

               Hub "Resources" doesn't meet compute requirement:

               MemoryMBMin:819, mandatory:true, checkMinHostCapacity:false.

                -

                The operation failed because no suitable resource was found.

               Hub "Resources" doesn't meet compute requirement:

               MemoryMBMin:819, mandatory:true, checkMinHostCapacity:false.

                -

                PlacementException NO_FEASIBLE_PLACEMENT_SOLUTION

 

 

 

This error seems to indicate that there are not enough memory ressources available in the "DEST" pool.

 

The VDC in which the VM I am trying to migrate is sitting is an "Allocation pool" and the parameter "Make Allocation pool Org VDCs elastic" is enabled in vCD.

 

My DEST cluster is new, not running any VM with a total of 1.35Tb of ram available.

 

Now, if you look at the attached screen shots, I noticed that my destination cluster is not displaying any "total" ressources but maybe it's normal ?

 

Of course, In the org VDC related to the VM I am trying to migrate, I defined all reservations on the lowest setting I could.

 

 

I feel I am missing something obvious but... what ?!?

 

Thanks !


Viewing all articles
Browse latest Browse all 4515

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>