VMware Cloud Community
N2Z2
Contributor
Contributor

Consolidate always required after snapshot deletion but only on one host

Hi all,

I have a cluster consisting of 4 esxi hosts 7.0.3 u3d

If I try to take a snapshot and then delete it, whatever vm I'm trying and only on host #7, it always prompts for consolidate after deletion. If you try to do the consolidate, the task completes without error but the consolidate does not work and the warning remains.

If I migrate the machine to another host the consolidate complete successfully. And if I do snapshot and delete it on another host, no consolidate is needed.

There are no communication problems between the vcenter and this specific host.

Any hint on this?

Thanks

Reply
0 Kudos
9 Replies
DavoudTeimouri
Virtuoso
Virtuoso

Hi,

Migrate virtual machine to another datatstore.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
N2Z2
Contributor
Contributor

I have already tried, but it does not work.

If the vm is on that host, the datastore or vm has no influence on the consolidation request.

Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso

Power-Off the VM and take clone from it on another datastore.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
N2Z2
Contributor
Contributor

The problem is for ALL the vm on that host, I should do the clone for, for example, 60 vm? And to which datastore? All the datastores have the same problem if the vm is on the host #7

Reply
0 Kudos
DavoudTeimouri
Virtuoso
Virtuoso

You said "The Machine". If you have problem with your all VMs on a host, migrate all virtual machines and reboot the host. Then move back one of virtual machines to the host and check the issue again.

-------------------------------------------------------------------------------------
Davoud Teimouri - https://www.teimouri.net - Twitter: @davoud_teimouri Facebook: https://www.facebook.com/teimouri.net/
Reply
0 Kudos
continuum
Immortal
Immortal

Check if your vmsd-files are invalid.
Open them in winscp--embedded-editor and if they dont match your situation assume they are invalid.
Invalid vmsd may result in ESXi and automatic backuptools misjudging the current configuration.
This results in stupid messages or failed operations.

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
N2Z2
Contributor
Contributor

The problem is due to a vmware bug, CBT module is not correctly loaded during esxi boot (source: vmware support).

 

Reply
0 Kudos
continuum
Immortal
Immortal

Did VMware support give you a command to load the CBT module manually ?
Which ESXi version is affected ?

 

 


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
N2Z2
Contributor
Contributor

I've seen the error in 7.0.3 3d and 7.0.3 3e, but it looks like it's present since 7.0.1 with Dell customization.

https://kb.vmware.com/s/article/81397

Manually load CBT Module:

  • Verify if the cbt module is enabled: esxcli system module list --enabled=true | grep cbt
  • Verify if the cbt module is loaded : esxcli system module list --loaded=true | grep cbt
  • To Manually load the module: # vmkload_mod cbt
Reply
0 Kudos