virtualbox.org

Hi.
Running Windows 10 Build 10130 with a 10gb VirtualBox VM with Windows XP installed. It was running perfectly with a couple of older Windows programs installed that won't run in W10.
Then out of the blue it won't START - WindowsXP . Says it's [Powered Off]. I have two 'Shared Folders' running.
It eventually presents the message - "Creating Process For Virtual Machine", then this:

Failed to open a session for the virtual machine WinXP10.

Cannot load R0 module C:\Program Files\Oracle\VirtualBox/VBoxDDR0.r0: SUPR3LoadModule: supLoadModule returned VERR_LDR_MISMATCH_NATIVE (VERR_LDR_MISMATCH_NATIVE).

Failed to register ourselves as a PCI Bus (VERR_MODULE_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}

Windows 10 is not a supported host just yet because it's still in beta. But if you attach the vbox.log (compressed) for the guest someone will most likely look at it.

Right click the VM in the VirtualBoxGUI. Select "Show Log". Save "VBox.log" to a file. Compress that file and attach it to a message here. Make sure the VM is fully shut down beforehand.

I believe LDR_MISMATCH_NATIVE means that you have a saved state that doesn't match the current host. You should shut VMs down before doing something as wild as changing hosts.

Now, your only option is to discard the saved state.

mpack wrote:I believe LDR_MISMATCH_NATIVE means that you have a saved state that doesn't match the current host. You should shut VMs down before doing something as wild as changing hosts.

Now, your only option is to discard the saved state.

Does that mean I lose the whole VM and have to reinstall WinXP?

No. A "saved state" is very similar to the "hibernate" function of Windows. When you restart the PC after hibernating you (hopefully) get put back into the OS at exactly the same place where the OS was when you hibernated, with all your programs and data still open and ready to use. Save-state is the same thing for a virtual machine, except that the OS in the guest does not know it was stopped.

When you discard the saved state, you dump all the info telling Virtualbox how to get the guest back to the point it was at when you stopped the guest. It's equivalent to pulling the plug on the PC and plugging it back in & booting up again. The guest will now reboot in the usual full-restart fashion, like it would after a regular shutdown or reboot.

All the unsaved data you were working with when you save-stated the guest will be lost. But the data and programs stored to the virtual disk will still be there. The only way to not lose that unsaved data is to put the guest back on the host it came from, start it form the saved state, and do a normal shutdown. Then move the guest back.

Well finally got that sorted.
What a drama. It turned out to be a 'shared folder' so deleted the share it loaded OK. Reset the shares and all good. But will make sure I do a proper 'Shut Down' of WinXP in the VM from now on

The real downside of this mistake is that 1 of the older programs that won't run on Win10 is Nuance PDF Professional 6 (the other 2 are CorelDraw7 and QuickVerse 4).
I had Nuance PDF Professional 6 loaded in the WinXP VM and working fine. But owing to VirtualBox not working I loaded it onto my laptop and inadvertently exceeded the 5 activations. Now I can't open it in the VM or anywhere else, so really annoyed at that. It was a great PDF manipulator.

Thanks for your help.

Larry

That should be a simple matter to fix. When that happened to me I contacted the company and they got me to identify the spurious activations so those could be disabled on their server. The good companies are well aware that single user (personal use) doesn't mean a single PC.

Even Microsoft will if you ask them nicely.

Well I did everything Nuance's support web sight said to do. No go.
So I called their 1300 number and was told that they didn't and wouldn't support that version any more and that I needed to buy the latest version as it was legacy software now. I tried to reason, very reasonably, but the guy just shouted me down then hung up.

Needless to say I won't be buying the latest version of anything from Nuance ever again.

Anyway, VirtualBox is working fine as long as I start it as an Administrator.

Thanks for your help everyone.

I've been having the same problem. Thought I solved it with a dll file but the problem came back. Today I have gotten my VM running by going to System -> Acceleration -> Paravirtualization = Default. It was legacy.

Hopefully that's a solid fix and can help others ...

Problem came back again. I had 'saved' the VM and rebooted because Microsoft tried to install the wrong NVidia driver.

I now have it running, I deleted the ".sav" file and altered the .vbox file to not reference the .sav file. Looks good for now ...

Larry3020 wrote:Well finally got that sorted.
What a drama. It turned out to be a 'shared folder' so deleted the share it loaded OK. Reset the shares and all good. But will make sure I do a proper 'Shut Down' of WinXP in the VM from now on

The real downside of this mistake is that 1 of the older programs that won't run on Win10 is Nuance PDF Professional 6 (the other 2 are CorelDraw7 and QuickVerse 4).
I had Nuance PDF Professional 6 loaded in the WinXP VM and working fine. But owing to VirtualBox not working I loaded it onto my laptop and inadvertently exceeded the 5 activations. Now I can't open it in the VM or anywhere else, so really annoyed at that. It was a great PDF manipulator.

Thanks for your help.

Larry

Thank you, Thank you, thank you Larry. Removing the shared folders fixed my problem as well so I can use Vbox on Win 10 with my existing VMs.

This is what i did:

System -> Acceleration -> Paravirtualization = Hyper-V
Since I use Intel CPU and it was at Default.
Now it is running smoothly.