He created the new folder for us and told me I have to "Enter Maintenance mode" on each ESXi host and then I can drag and drop them from old folder to the new folder.
Everything went smoothly. Just need to make sure VMs need to be powered OFF first before the ESXi hosts can enter maintenance mode.
After moving all ESXi hosts from old to new folder, I was able to start VMs except the last VM. It is complaining about swap space. After some research online, I found the following URL:
http://kb.vmware.com/selfservice/micros ... Id=1030719
The last bullet under Resolution section has:
Code: Select all
Create a memory reservation with the same size as the memory assigned to the virtual machine. This prevents the creation of a swap file. For more information, see the Resource Management Guide.
Some time ago, when I was trying to migrate (vMotion) VMs from one host to another, I remember seeing issues and VMWare suggested me to remove the reservation and I was able to migrate. Following is the email thread with Tim Schulte:
Code: Select all
On Jul 2, 2013, at 5:36 PM, "Hsiao, Chang-An" <chang-an.hsiao@medtronic.com> wrote:
I did a few more tests.
I had to clear the checkbox of “Reserve all guest memory (All locked)” before I can remove the reservation.
Then, I was able to migrate without the error message.
Thanks a lot for your tip, Tim!!
Chang-An
From: Tim Schulte [mailto:schultet@vmware.com]
Sent: Tuesday, July 02, 2013 3:02 PM
To: Hsiao, Chang-An; Jeff Whitman
Subject: Re: VMWare vMotion question
Possibly. Jeff what are your thoughts on this?
Thanks
Tim
On Jul 1, 2013, at 10:09 PM, "Hsiao, Chang-An" <chang-an.hsiao@medtronic.com> wrote:
Parent resource pool?
The server has only one VM and we didn’t set up a parent resource pool for the VM then.
For the VM, we do have a reservation (all, 251816 MB).
Should I remove the reservation or limit?
Thanks!
Chang-An
From: Tim Schulte [mailto:schultet@vmware.com]
Sent: Monday, July 01, 2013 5:40 PM
To: Hsiao, Chang-An
Subject: Re: VMWare vMotion question
Hi Chang-An,
By the looks of the error message, it sounds like perhaps the resource pool has a reservation or limit set on it? This would prevent a VM from failing over.
Have you checked the parent resource pool for any reservations or limits?
Thanks
Tim Schulte | Senior Technical Account Manager | VMware, Inc. | schultet@vmware.com | Mobile: 612-360-5671
**I will be OOTO: July 8, Aug 5-9 [vacation] **
From: "Hsiao, Chang-An" <chang-an.hsiao@medtronic.com>
Date: Mon, 1 Jul 2013 17:26:50 -0700
To: Tim Schulte <schultet@vmware.com>
Subject: FW: VMWare vMotion question
Hi, Tim:
I just realized that Tonja is out of office until next week.
Can you help us find resources for the following situation?
Thanks in advance!
Chang-An
From: Hsiao, Chang-An
Sent: Monday, July 01, 2013 5:24 PM
To: 'Tonja Hedemark'; 'jehitman@vmware.com'
Cc: Khedagi, Mohan [ITG]; Qureshi, Manzar
Subject: VMWare vMotion question
Hi, Tonja and Jeff:
This is Chang-An Hsiao from Medtronic.
I was trying to do a VM failover (vMotion/migrate) test on our SAP CI/DB VM from one server to another (identical UCS C460s).
VM is hosted on server A with allocated memory of 251618 MB.
The destination server B has 262026 MB (more than VM needs) available for us (no other VMs on server B).
When I was trying to migrate from server A to server B, it complained about:
The available memory resources in the parent resource pool are insufficient for the operation.
I couldn’t figure out why 262026 MB is insufficient for 251618 MB.
Can you help?
Chang-An Hsiao
Medtronic Diabetes - IT
(818)576-4304