virtualbox.org

A few days ago i've upgraded virtualbox to 4.3.4 version but it hasn't allowed me to open the VM (with Linux). The problem was a little bit boring 'cause virtualbox showed me an error requiring the virtualization in the CPU configuration, but since my BIOS Utility has not the CPU configuration i couldn't enable it. So i downgraded Virtualbox to previous version, but another error came out:

"Unsupported version 14 of data unit 'cpum' (instance #1, pass 0xffffffff)
(VERR_SSM_UNSUPPORTED_DATA_UNIT_VERSION).
Details
Exit Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}"


This is my PC configuration:
PC: HP Presario CQ56
CPU: Pentium(R) Dual-Core T4500 2.3 GHz
OS: Windows 7 Home Premium 64 bit


I have no idea of how solve this problem, can you help me? Thank you so much!

Upgrade to 4.3.4 then run the following to get the guest to work.

It looks like you may have saved a state using a later version of the software. Discard the saved state and it may work.

mpack wrote:It looks like you may have saved a state using a later version of the software. Discard the saved state and it may work.

I need that saved state!

Perryg wrote:Upgrade to 4.3.4 then run the following to get the guest to work.

Code: Select all

VBoxManage modifyvm <VmName> --longmode off

Where/how can I run that code? I can't access to Linux.
Thank you!

That code is run on the host and in a command windows on MSWindows
You will need to be in the directory that has VBoxManage.exe for it to work.

Perryg wrote:That code is run on the host and in a command windows on MSWindows
You will need to be in the directory that has VBoxManage.exe for it to work.

Ok, now I'm not at home so tomorrow I'll try and I'll let you know. Thank you

Perryg wrote:Upgrade to 4.3.4 then run the following to get the guest to work.

Code: Select all

VBoxManage modifyvm <VmName> --longmode off

Perryg I did it but it doesn't work. I attach you the entire error. Anyway it said me "Could not find a reigstered machine named 'Linux'", but my VM is named Linux! (actually it's named Linux FoI)

Post the guests log file ( as an attachment )

When a command line argument contains spaces, such as "Linux FoI", then you need to wrap it in quotes like I just did.

Perryg wrote:Upgrade to 4.3.4 then run the following to get the guest to work.

Code: Select all

VBoxManage modifyvm <VmName> --longmode off

that worked for me, thx

Perryg wrote:Post the guests log file ( as an attachment )

done

mpack wrote:When a command line argument contains spaces, such as "Linux FoI", then you need to wrap it in quotes like I just did.

Ok thank's i did it, but "the machine is not mutable" 'cause the state is saved. So ultimately i have no other alternatives: i have to discard the saved state

The whole issue here is that you need to change that setting, but the machine is not mutable since it is in saved state.
I don't know what else you can do at this point.

Perryg wrote:I don't know what else you can do at this point.

Perhaps revert to his old VirtualBox version, shut the VM down properly and apply the longmode fix.

Maybe but they said that they had already tried that ( original post ). Not sure what version they were using though which may be part of it.

mpack wrote:

Perryg wrote:I don't know what else you can do at this point.

Perhaps revert to his old VirtualBox version, shut the VM down properly and apply the longmode fix.

The command prompt said me: VBoxManage.exe: error: Unknown option: --longmode
But before it knew it!
I think it's because of the old version, but why? maybe in that version was not implemented an answer to the --longmod command.