virtualbox.org

HI,
after updatin my VBox install from 4.1.8 to 4.1.10, all my VM, regardless of their position, refuse to start with error:

Apertura di una sessione per la Macchina Virtuale XP-ITA non riuscita.

Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE).

Codice 'uscita: E_FAIL (0x80004005)
Componente: Console
Interfaccia: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}

The log of the failed start looks like this:

VirtualBox 4.1.10 r76836 win.x86 (Mar 14 2012 18:56:08) release log
00:00:00.862 Log opened 2012-03-26T07:46:33.167628800Z
00:00:00.862 OS Product: Windows 7
00:00:00.862 OS Release: 6.1.7601
00:00:00.862 OS Service Pack: 1
00:00:00.863 Host RAM: 3509MB RAM, available: 1600MB
00:00:00.863 Executable: C:\Program Files\Oracle\VirtualBox\VirtualBox.exe
00:00:00.863 Process ID: 3692
00:00:00.863 Package type: WINDOWS_32BITS_GENERIC
00:00:00.863 Installed Extension Packs:
00:00:00.863 Oracle VM VirtualBox Extension Pack (Version: 4.1.10 r76795; VRDE Module: VBoxVRDP)
00:00:00.878 pdmR3LoadR0U: pszName="VMMR0.r0" rc=VERR_LDR_MISMATCH_NATIVE szErr="supLoadModule returned VERR_LDR_MISMATCH_NATIVE"
00:00:00.878 VMSetError: D:\tinderbox\win-4.1\src\VBox\VMM\VMMR3\VM.cpp(591) vmR3CreateU; rc=VERR_LDR_MISMATCH_NATIVE
00:00:00.878 VMSetError: Failed to load VMMR0.r0
00:00:00.878 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={Failed to load VMMR0.r0 (VERR_LDR_MISMATCH_NATIVE)}, preserve=false
00:00:00.963 Power up failed (vrc=VERR_LDR_MISMATCH_NATIVE, rc=E_FAIL (0X80004005))
00:00:01.318 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={1968b7d3-e3bf-4ceb-99e0-cb7c913317bb} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false

This happens on EVERY VM I have on the system, regardless of their O/S (Linux, XP, Win7, FreeDos) actually it stops even before the Bios splashscreen, and of VM position (some VM are on an external HD because I move them between different PC, moving an external HD is a lot easier than having to bring a laptop with you).
There are no errors when I look in the virtual images manager, all disks appear to be accessible and consistant.

As soon as I disinstall 4.1.10 and install 4.1.8, all VMs work fine again, so I don't think there's any issue with the VM themselves. I already tried installing the new version several times, but I've always had the same issue

Someone has any idea?

This sounds like 4.1.10 didn't get installed correctly, but it's hard to tell why. This doesn't appear to be a widespread issue so there may be something unusual about your system.

There's nothing wrong with the VMs but the internal VirtualBox components don't match for whatever reason.

You could collect more information as detailed here: https://www.virtualbox.org/wiki/MSI_Logging

Exact same issue for me.

Aside from running 'As Administrator', I fixed this by doing the following:

1. Navigate to C:\Users\<Me>\AppData\Local\VirtualStore\Program Files\Oracle
2. Rename the VirtualBox folder that lives there to VirtualBox_OLD

Regards,

Oli

I've tried installing with the log as per the instruction in the linked page, but unfortunately I was unable to find the log file produced (even If i tried looking in the local user and administrator)

I've tried the other technique, and I found out the VirtualBox dir in C:\Users\<Me>\AppData\Local\VirtualStore\Program Files\Oracle reported dates preceding my attempts to install the 4.1.10, so it was actually not touched during de update process.

Renaming it allowed me to run my VM, thanks.

Upgrading to 4.1.12 from 4.1.10: Same error, same workaround.

Upgrading to 4.1.14 from 4.1.12: Same error, same workaround.

Upgrading to 4.1.16 from 4.1.14: Same error, same workaround.

There's a trend here...

Yep, the trend is that you still haven't found out what's wrong with your system.

All VMs refuse to start, host is Linux/Debian. This happened after upgrade to 4.1.18, from previously released (i do regular upgrades as new versions appear) version, which was i think 4.1.16 (not sure).

Given my host is Linux, and the above ones are Windows, this suggest there could be a problem with Virtualbox, and not with the systems.

Problems persists after returning to 4.1.16, which suggest problem with the system, not with Virtualbox.

solved. the problem was in recently upgraded gcc4.7.

had to go down to gcc4.6 (in Debian testing), reinstall virtualbox (to rebuild virtualbox kernel modules), and then it was fine.

Picked up idea here at several places (but forum won't let me paste URLs before i was a member for a day ... and had a post ... silly).

Someone described the problem well: "I got two progress bars, one at 0% other at 20% and zombie unclosable window of hanged VM."

Win7 host, upgrade from 4.1.4 to 4.1.18- same problem but I couldn't use the workaround - no Oracle folder in VirtualStore/Program Files.

So I ran the installation for 4.1.18 again and chose the Repair option.
That seems to fix the problem - now my VMs are working on 4.1.18.