nerdexam
Broadcom-VMware

2V0-622 · Question #278

An administrator is attempting to power on a virtual machine with 32GB of memory. The operation fails with the following error: Could not power on VM : No space left on device Checking the space on th

The correct answer is A. Set a 2GB memory reservation on the VM.. The 'No space left on device' error during VM power-on occurs because vSphere cannot allocate the required memory swap file on the datastore, and a memory reservation reduces the swap file size needed.

Section 8 – Deploy and Administer VMware Virtual Machines

Question

An administrator is attempting to power on a virtual machine with 32GB of memory. The operation fails with the following error:

Could not power on VM : No space left on device Checking the space on the virtual machine's datastore, there is 30GB free. Which action would allow the VM to power on?

Options

  • ASet a 2GB memory reservation on the VM.
  • BMount the virtual disk from the affected VM on to another virtual machine and free up space from
  • CEnable vSphere HD admission control on the cluster in which the VM resides.
  • DSet a 2GB memory limit on the VM.

How the community answered

(22 responses)
  • A
    59% (13)
  • B
    23% (5)
  • C
    14% (3)
  • D
    5% (1)

Why each option

The 'No space left on device' error during VM power-on occurs because vSphere cannot allocate the required memory swap file on the datastore, and a memory reservation reduces the swap file size needed.

ASet a 2GB memory reservation on the VM.Correct

When a VM powers on, vSphere creates a swap file (.vswp) sized at configured memory minus memory reservation; with 32 GB configured and zero reservation, a full 32 GB swap file is required, which exceeds the 30 GB available on the datastore. Setting a 2 GB memory reservation reduces the required swap file size to 30 GB (32 GB - 2 GB), matching the available datastore space and allowing the VM to power on. This is why reservations directly affect the on-disk swap file footprint.

BMount the virtual disk from the affected VM on to another virtual machine and free up space from

Mounting the VM's virtual disk on another VM and freeing guest OS space addresses in-guest disk usage, not the host-level .vswp swap file that vSphere must create on the datastore at power-on.

CEnable vSphere HD admission control on the cluster in which the VM resides.

vSphere HA admission control reserves cluster resources for failover scenarios and has no effect on the datastore space required to create a VM's memory swap file.

DSet a 2GB memory limit on the VM.

A memory limit caps the maximum memory the VM can actively use at runtime but does not reduce the size of the swap file, which is governed by the memory reservation setting, not the limit.

Concept tested: Memory reservation reducing VM swap file size on datastore

Source: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.resmgmt.doc/GUID-B8EC0D3C-92E2-4975-8D17-76ADAB0D8DB0.html

Topics

#VM power on failure#memory reservation#swap file#datastore space

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 2V0-622 Practice