ESXi 6.7 Error: Failure to restore virtual machine blah3 to snapshot blah3-virgin

[JohnMasinter]

Summary:

I have a fresh install of ESXi 6.7, properly licensed.

When I try to restore a snapshot, I get this error:

"Failed to restore virtual machine blah3 to snapshot blah3-virgin"

Detail:

I installed a few versions of our generic Linux and saved snapshots after each install.

I do not need a running state snapshot saved, so I power off and save without memory.

1. installed ver blah1, then power off, then save snapshot

2. installed ver blah2, then power off, then save snapshot

3. installed ver blah3, then power off, then save snapshot

4. THEN with VM powered off, try to restore any of these snapshots from snapshot manager,

and I get the error above. Also note that when I select (click on) a snapshot in snapshot manager,

before I click "Restore", the preview box just has a spinner that never stops spinning.

Any tips? Thank you!

--John

[JohnMasinter]

Here are some screen shots:

[daphnissov]

Interesting. Once powered off, could you attach the VMware.log file which is found in this vm's home directory?

[JohnMasinter]

Here are the last 50 lines are so in the vmware.log file:

2018-08-31T13:24:07.858Z| vmx| I125: OvhdMem: memsize 1024 MB VMK fixed 3462 pages var(mem) 529 pages var(cpu) 8 cbrcOverhead 0 pages total

3999 pages

2018-08-31T13:24:07.858Z| vmx| I125: VMMEM: Maximum Reservation: 215MB (MainMem=1024MB) VMK=15MB

2018-08-31T13:24:07.878Z| vmx| I125: ToolsISO: Selected Tools ISO 'linux.iso' for 'other4xlinux-64' guest.

2018-08-31T13:24:07.879Z| vmx| I125: MsgHint: msg.tools.toolsImage

2018-08-31T13:24:07.879Z| vmx| I125+ The VMware Tools package is not running in this virtual machine. The package might be necessary for the

guest operating system to run at resolutions higher than 640x480 with 16 colors. The package provides significant performance benefits as w

ell. To install it, choose VM > Install VMware Tools… after the guest operating system starts.

2018-08-31T13:24:07.879Z| vmx| I125+ VMware ESX can remind you to install the VMware Tools package when you power on the VM. Select OK to en

able the reminder.

2018-08-31T13:24:07.879Z| vmx| I125+ ---------------------------------------

2018-08-31T13:24:07.882Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'MKS' (cmd=queryFields)

2018-08-31T13:24:07.890Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'MKS' (cmd=queryFields)

2018-08-31T13:24:07.893Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'NVDimm' (cmd=queryFields)

2018-08-31T13:24:07.897Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'Parallel' (cmd=queryFields)

2018-08-31T13:24:07.899Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'Serial' (cmd=queryFields)

2018-08-31T13:24:07.900Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'NVDimm' (cmd=queryFields)

2018-08-31T13:24:07.914Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'Hbr' (cmd=queryFields)

2018-08-31T13:24:07.916Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'MKS' (cmd=queryFields)

2018-08-31T13:24:07.928Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'MKS' (cmd=queryFields)

2018-08-31T13:24:07.928Z| vmx| I125: Vigor_ClientRequestCb: failed to do op=3 on unregistered device 'MKS' (cmd=queryFields)

2018-08-31T13:24:07.931Z| vmx| I125: TOOLS INSTALL User requested VMware Tools installation reminder

2018-08-31T13:24:07.931Z| vmx| A100: ConfigDB: Setting tools.remindInstall = "TRUE"

2018-08-31T13:24:07.933Z| vmx| I125: Tools: ToolsRunningStatus_Exit, delayedRequest is 0x72CC7A1670

2018-08-31T13:24:07.933Z| vmx| I125: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do

2018-08-31T13:24:07.937Z| vmx| I125: USB: Disconnecting device 0x10e0f0002

2018-08-31T13:24:07.939Z| vmx| I125: Destroying virtual dev for scsi0:0 vscsi=8206

2018-08-31T13:24:07.939Z| vmx| I125: VMMon_VSCSIStopVports: No such target on adapter

2018-08-31T13:24:07.940Z| vmx| I125: MKS thread was already stopped

2018-08-31T13:24:07.940Z| mks| I125: MKSControlMgr: Remove VNC connection 1

2018-08-31T13:24:07.940Z| mks| I125: SOCKET 11 (114) Sending websocket close frame, status code = 1000

2018-08-31T13:24:07.942Z| mks| I125: MKS-RenderMain: Stopping MKSBasicOps

2018-08-31T13:24:07.942Z| mks| I125: MKS PowerOff

2018-08-31T13:24:07.942Z| mks| I125: MKS thread is exiting

2018-08-31T13:24:07.942Z| vmx| I125: SVMotion_PowerOff: Not running Storage vMotion. Nothing to do

2018-08-31T13:24:07.942Z| vmx| I125: scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

2018-08-31T13:24:07.943Z| vmx| I125: Closing disk 'scsi0:0'

2018-08-31T13:24:07.945Z| vmx| I125: DISKLIB-VMFS  : "/vmfs/volumes/5b89257d-8b459174-6327-001e677c40c6/MLOS3/MLOS3-000008-sesparse.vmdk" : closed.

2018-08-31T13:24:07.952Z| vmx| I125: DISKLIB-VMFS  : "/vmfs/volumes/5b89257d-8b459174-6327-001e677c40c6/MLOS3/MLOS3-flat.vmdk" : closed.

2018-08-31T13:24:07.955Z| vmx| I125: Vix: [mainDispatch.c:1180]: VMAutomationPowerOff: Powering off.

2018-08-31T13:24:07.955Z| vmx| I125: Vix: [mainDispatch.c:1220]: VMAutomation: Leaving module running until next state change.

2018-08-31T13:24:07.956Z| vmx| I125: WORKER: asyncOps=6609 maxActiveOps=1 maxPending=0 maxCompleted=0

2018-08-31T13:24:07.981Z| vmx| I125: Vix: [mainDispatch.c:4239]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0

2018-08-31T13:24:07.981Z| vmx| I125: Vix: [mainDispatch.c:4258]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.

2018-08-31T13:24:07.981Z| vmx| A100: ConfigDB: Setting cleanShutdown = "TRUE"

2018-08-31T13:24:07.983Z| vmx| I125: Vix: [mainDispatch.c:4239]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

2018-08-31T13:24:07.983Z| vmx| I125: Vix: [mainDispatch.c:4258]: VMAutomation: Ignoring ReportPowerOpFinished because the VMX is shutting down.

2018-08-31T13:24:07.983Z| vmx| I125: Transitioned vmx/execState/val to poweredOff

2018-08-31T13:24:07.983Z| vmx| I125: VMX idle exit

2018-08-31T13:24:07.987Z| vmx| I125: Vix: [mainDispatch.c:832]: VMAutomation_LateShutdown()

2018-08-31T13:24:07.988Z| vmx| I125: Vix: [mainDispatch.c:781]: VMAutomationCloseListenerSocket. Closing listener socket.

2018-08-31T13:24:07.988Z| vmx| I125: Flushing VMX VMDB connections

2018-08-31T13:24:07.989Z| vmx| I125: VigorTransport_ServerCloseClient: Closing transport 72CC505CB0 (err = 0)

2018-08-31T13:24:07.989Z| vmx| I125: VigorTransport_ServerDestroy: server destroyed.

2018-08-31T13:24:07.989Z| vmx| I125: VMX exit (0).

2018-08-31T13:24:07.990Z| vmx| I125: OBJLIB-LIB: ObjLib cleanup done.

2018-08-31T13:24:07.990Z| vmx| I125: AIOMGR-S : stat o=4 r=25 w=3 i=0 br=156156 bw=384

2018-08-31T13:24:07.990Z| vmx| W115: VMX has left the building: 0.

[a_p_ · Accepted solution]

Welcome to the Community,

Only a thought.

The Revert function tries to restore everything to the point-in-time state. I see that you have an ISO image attached to the VM. Can you confirm that this, or other previously used ISO images still exist in the location /folder, in which they were at the time when you created the snapshot?

André

[JohnMasinter]

SOLVED!

Thank you Andre!

You are correct, I was taking the snapshot with the iso image attached as the virtual cd device.

Now I disconnect the iso, and return the cd device to the native device, and THEN take the snapshot.

This has solved the issue.

The sad part is that I had this same trouble 5 years ago with ESXi 5.x, and somehow forgot that lesson since that time.

--John