Which three things can be done to allow more virtual machines to be deployed into the cluster from this templa

A company has been utilizing templates in its environment. It is running a 10-node ESXi 5.x Cluster and DRS has not been configured. Several virtual machines have been deployed from this template and successfully powered on, but a newly deployed virtual machine will not power on. There appears to be adequate CPU and Memory resources available on the host. Which three things can be done to allow more virtual machines to be deployed into the cluster from this template? (Choose three.)

A.
Deploy the virtual machine to a different host using the same datastore

B.
Enable DRS on the cluster to balance the virtual load out across hosts

C.
Increase the virtual machine memory reservation

D.
Move the swap file to a different location

E.
Select a different datastore for the virtual machine

Explanation:
Quote from KB:
If you make reservations for your virtual machine’s that are equal to the amount of RAM assigned to them, swapping and page sharing does not occur. You can over commit pretty heavily if you are comfortable with poorer performance. If you do not set reservations, ESX host creates a .vswp file equal to the difference between the amount of physical memory assigned to the virtual machine and the reservation it has. By default, memory reservations are set to 0. If you have a virtual machine with 2GB of memory without a reservation, it creates a 2GB .vswp file when it is powered on. The virtual machine starts using the .vswp file if the server is out of physical RAM. If you set a 1GB reservation, it creates a 1GB .vswp file. The .vswp files are what allows for memory overcommitment.

7 Comments on “Which three things can be done to allow more virtual machines to be deployed into the cluster from this templa

  1. George Kenny says:

    Answers in green are incorrect, question asks for THREE answers, there are 4 highlighted.

    The three correct answers are C, D & E as the vm is being vswap constrained – moving to another host will not fix the issue as the swap directory is being exhausted.

  2. Per olsson says:

    The´re mentioning everything BUT storage. That is why there is issues with storage.
    And “A” and “E” is the opposite to each other. So that can´t be right either.

    1. acslater1 says:

      Increasing the memory reserve has the ability to completely knock out the swap file if the reserve equals the memory allocation. Since there is enough memory available this is a viable option. Pretty much accomplishes the same thing as D in that the swap file is removed from the datastore.

  3. Rich says:

    I wish these questioned and answers were at least a little realistic! Answer E is the only realistic one. If you’re that low on disk space reducing or removing the swap file is nonsense. You have a major disk space usage problem to deal with.


Leave a Reply

Your email address will not be published. Required fields are marked *