VVOL VMs Crash After vMotion
search cancel

VVOL VMs Crash After vMotion

book

Article ID: 314673

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Following a vMotion operation, the VVOL VMs were found to be in a powered-off state, requiring further investigation.

Environment

VMware vSphere ESXi 6.7

Cause

CBT was enabled on the VVOL VM, but a reboot did not occur as expected. This configuration change is unsupported in VVOL environments.

Resolution

Enabling Change Block Tracking (CBT) on a VVOL VM requires not only setting the CBT flag but also restarting the VM for the configuration to take effect. While setting the flag alone marks the VM for CBT, the actual activation occurs during a shutdown or reboot.

To avoid this issue, follow these steps:

  1. Enable CBT on the VVOL VM.
  2. Reboot the VVOL VM.
  3. Allow the VM to fully power on and stabilize before performing any vMotion activities.

By following these steps, you ensure proper CBT activation and avoid unexpected behavior during vMotion or other operations.

Powered by Wolken Software