Powering on the virtual machine or the creating a snapshots fails when a 4GB file is placed on Config-vvol

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Powering on the virtual machine fails with the error:

 Transport(VMDB)error-45 :Failed to connect to peer process

• Creation of snapshot fails with the error:

An error occurred while taking a snapshot :Unable to save snapshot file.
An error occurred while saving snapshot file "/vmfs /volumes/ vvol :***********/vm-Snapshot6. vmsn "
An error occurred while saving :There is no space left on the device.

Environment

VMware vCenter Server 6.7.x
VMware vCenter Server Appliance 6.0.x
VMware vCenter Server Appliance 6.7.x
VMware vCenter Server 6.5.x
VMware vCenter Server Appliance 6.5.x
VMware vCenter Server 6.0.x

Cause

In general, config-VVol includes the VM configuration file, virtual disk, snapshot descriptor files, log files, and lock files.

By default, the general contents of config-VVol consume only a very small portion of this 4GB allocation. If any other large-size files such as image files exist, or if the log file is enlarged, config-VVol may exceed the 4GB limit.

Resolution

To resolve this issue, remove unnecessary files from the virtual machine home directory, and secure enough capacity that is required to create a config-VVOL file.

In addition, perform the rotate setting as not to expand the log of the virtual machine,see  Configuring Logging Levels for the Guest Operating System.

Update: Starting with 7.0 u2 it is possible for partners to increase the config vVol to above 4 GB. Please work with your vVol partner on implementing this if it is supported by your partner and applicable to your environment.