Snapshot quiescing fails on Linux guests

  • Linux based virtual machines fail to take quiesced snapshots after upgrading ESXi and VMware Tools to 5.1.
  • Using the vSphere Client to take a quiesced snapshot fails immediately with the error:

The guest OS has reported an error during quiescing. The error code was: 3 The error message was: Error when enabling the sync provider.

  • The hostd.log of the host running the virtual machine contains errors similar to:

[3CB9EB90 verbose ‘vm:/vmfs/volumes///.vmx’] Handling message _vmx##: The guestOS has reported an error during quiescing.
–> The error code was: 3
–> The error message was: Error when enabling the sync provider.

Cause

This issue occurs due to a problem with the FIFREEZE/FITHAW ioctl feature within the guest that is utilized to quiesce the Linux filesystem, affecting kernel 2.6.32-24 and lower.

Resolution

To resolve this issue, update the kernel of your Linux guest virtual machine to 2.6.35-22 or higher.

To work around this issue without updating the kernel:

  1. Open the tools.conf file, located in the /etc/vmware-tools directory, using a text editor.

Note: If the tools.conf file does not exist, create a new, empty file.

  • Add these lines to the file:

[vmbackup]
enableSyncDriver = false

Posted in: Vmware.
Last Modified: October 4, 2013

3 thoughts on “the guest os has reported an error during quiescing. the error code was 3 in linux machines

  1. S

    The resolution you are offering only works because it disables the quiescing.
    After setting syncdriver to false the backups are only crash consistent

    1. Alex Hunt Post author

      The other option can be upgrading the Linux kernel if you dont want to set syncdriver to false. Every environment has different mechanism for taking the VM backups, so it is not necessary that backup will crash for every software.

  2. S

    There doesn’t seem to be a kernel update high enough to solve this with centos 6.7
    The problem seems to be related to FIFREEZE/FITHAW ioctl in the kernel.
    I’m trying to determine whether disabling syncdriver (VMware quiescing module) actually solves the conflict and the quiescing is handled correctly by Linux kernel.
    Or if quiescing really is disabled completely.

Leave a reply