virtualbox.org

I've got a Windows 7 VM with a couple of saved snapshots. I discovered recently that I couldn't restore the snapshots anymore. The restoring progress bar goes up for a while, but then the VM is closed and I get this error:
---
Failed to open a session for the virtual machine DV.

pgm#1: Failed to locate a MMIO2 range called 'Hyper-V TSC page' owned by GIMDev/0, region 1 [ver=14 pass=final] (VERR_SSM_LOAD_CONFIG_MISMATCH).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
---
The only thing I could think of that might have messed something up was that I was fiddling around with Android emulators, installing and removing Andy and BlueStacks. I tried installing VirtualBox 5.0.6 (I think it was 5.0.2 before) with extensions and guest additions, but the same thing happens.

Is there any way to fix this without losing the snapshot? I managed to get it to boot from scratch, but it's the snapshot that's essential to me. Any help would be greatly appreciated. I attached the log (zip because of 128kb limit).
Thanks

You did the right thing by zipping the log file, but it seems to be corrupted. Could you try it again please?

  $ file ~/Desktop/DV-2015-10-04-16-15-21.zip
  ~/Desktop/DV-2015-10-04-16-15-21.zip: data

Edit: I was able to open the zip from the command line, no need to re-post it. No clue why Dbl-clicking (Archive Utility) failed, while from the command line (unzip) it simply worked. Beats me...

VERR_SSM_LOAD_CONFIG_MISMATCH
The snapshot seems to contain a saved state which is not compatible?

Your VM was configured with Hyper-V while you saved the state. However, while restoring, the paravirtualization provider is set to "None". How did you change the VM config. for a saved state? The VirtualBox GUI certainly doesn't allow changing this setting for a saved-state of a VM.

Ramshankar wrote:Your VM was configured with Hyper-V while you saved the state. However, while restoring, the paravirtualization provider is set to "None".

Would you mind sharing the knowledge on how you were able to detect that information from the log file?

Well, Ramshanker may have other clues, but Hyper-v is mentioned in the OPs error message, but "Hypervisor present" is not set as a guest flag in the log file.

socratis wrote:

Ramshankar wrote:Your VM was configured with Hyper-V while you saved the state. However, while restoring, the paravirtualization provider is set to "None".

Would you mind sharing the knowledge on how you were able to detect that information from the log file?

GIM - Guest Interface Manager (the component that deals with paravirtualization providers)
PGM - Paging Manager & Monitor (the component that deals with guest memory and paging)

VMs configured with a paravirt. provider always have a GIM device (GIMDev) attached to the VM automatically. This device, during VM initialization, may register special MMIO2 ranges of the guest memory for things like the Hyper-V TSC page, hypercall page etc. The error indicates that the saved state has these MMIO2 regions but PGM is unable to find a match for it in the current VM.

If you search the VBox.log for "GIM", you'll see no "GIMDev". This is because the VM is configured with GIM provider as "None" as can be seen from this log snippet:

mpack wrote:Well, Ramshankar may have other clues, but Hyper-v is mentioned in the OPs error message, but "Hypervisor present" is not set as a guest flag in the log file.

The HVP present bit is only a consequential indicator. You can set this bit even for VMs that don't have any paravirt. providers, as it's a hardware CPUID feature bit. The CFGM indicator of the paravirt. provider being configured for a VM is the line I quoted above from the VBox.log.

Ah, I see. Thanks for the info.

Ramshankar wrote:Your VM was configured with Hyper-V while you saved the state. However, while restoring, the paravirtualization provider is set to "None". How did you change the VM config. for a saved state? The VirtualBox GUI certainly doesn't allow changing this setting for a saved-state of a VM.

I don't think I did. I was looking at the .vbox file at some point when trying to figure out what the issue is but I don't believe I ever edited it. Are you suggesting that editing the .vbox file could help?

Could you please upload the .vbox file? It may be our bug...

Including the .vbox file - changed extension to txt, since file upload didn't allow vbox extension. Thanks for your help.