I'm trying to use QueryChangedDiskAreas on an ESX 4 server through the Perl SDK. The method I'm using works for some VMs, but for others, I get back a FileFault. Looking at the ESX server logs reveals this:
(me) Calling QueryChangedDiskAreas with snapshot: 64-snapshot-35, deviceKey: 2000, changeId: *
2010-04-05 16:57:20.316 F63A7B90 error 'vm:/vmfs/volumes/4b7da659-f2a39f3d-b04d-003048d5dbf0/NewVM/NewVM.vmx' Cannot compute changes for disk /vmfs/volumes/4b7da659-f2a39f3d-b04d-003048d5dbf0/NewVM/NewVM-000007.vmdk: Unknown change epoch.
2010-04-05 16:57:20.316 F63A7B90 info 'App' AdapterServer caught exception: vim.fault.FileFault
2010-04-05 16:57:20.316 F63A7B90 info 'Vmomi' Activation N5Vmomi10ActivationE:0x5dced698 : Invoke done queryChangedDiskAreas on vim.VirtualMachine:64
2010-04-05 16:57:20.316 F63A7B90 verbose 'Vmomi' Arg snapshot:
'vim.vm.Snapshot:64-snapshot-35'
2010-04-05 16:57:20.316 F63A7B90 verbose 'Vmomi' Arg deviceKey:
2000
2010-04-05 16:57:20.316 F63A7B90 verbose 'Vmomi' Arg startOffset:
0
2010-04-05 16:57:20.316 F63A7B90 verbose 'Vmomi' Arg changeId:
"*"
2010-04-05 16:57:20.316 F63A7B90 info 'Vmomi' Throw vim.fault.FileFault
This is on a VM with hardware version 7, and change tracking is enabled as far as I can tell. Any idea about what is causing this error? Is there something that is misconfigured for this particular VM, or am I calling it incorrectly? (I'm not sure what "unknown change epoch" is referring to.)
Thank you.