Author Topic: [SOLVED] Had to change CPU and now cannot open my VM  (Read 3489 times)

Offline Cressida

  • Sr. Member
  • ****
  • Posts: 283
[SOLVED] Had to change CPU and now cannot open my VM
« on: February 10, 2011, 01:13:34 PM »
My CPU died and I replaced it with a similar one that runs a slightly lower speed.

Now my Win-XP that runs in VM will not open and I get this error message :

Failed to open a session for the virtual machine Win-XP.
cpum#1: "CPU model" mismatch: host=0x2f saved=0x37 [ver=12 pass=final] (VERR_SSM_LOAD_CPUID_MISMATCH).

Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
Console
Interface:
IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}



    As you can see from the message, it appears that it is checking the CPU model number and noting a mismatch.  Any ideals on how to get it to overlook the change and let me open my VM?
« Last Edit: February 10, 2011, 03:11:51 PM by Cressida »
AMD Athlon 64 3200, 2GB ram,  ~320 GB HD,  Video=ATI Radeon X300 SE (128mb) PCI-e
KDE     Kern  3.2.18-pclos2.a64

I used to think I knew a lot about computers until I started using Linux.  Now I feel my age...

Offline T6

  • Super Villain
  • ******
  • Posts: 19077
  • xmas is comming!
Re: Had to change CPU and now cannot open my VM
« Reply #1 on: February 10, 2011, 01:51:23 PM »
this message, is generated by virtualbox or inside the virtual machine?

how many cores does it have? 

how many cores you assigned to the virtual machine?
"If you wish to make an apple pie from scratch, you must first invent the universe."

Carl Sagan

Offline Old-Polack

  • Administrator
  • Super Villain
  • *****
  • Posts: 11561
  • ----IOFLU----
Re: Had to change CPU and now cannot open my VM
« Reply #2 on: February 10, 2011, 01:59:18 PM »
Cressida:

Reinstall the same version of VirtualBox. The installation should pick up the current CPU and adjust for it. It will not affect the VDI file itself, so it should still be usable. You may have to create a new VM, but you would specify to use the existing VDI hard drive in that VM. I'm still using the same VDI files I created a couple of years ago, which have been used with three different hardware builds and numerous installed versions of VirtualBox.
Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...

Offline GermanTux

  • Hero Member
  • *****
  • Posts: 693
Re: Had to change CPU and now cannot open my VM
« Reply #3 on: February 10, 2011, 02:12:10 PM »
Cressida;

The easiest way to take care of this is to remove the XML header file that contains the info on the virtual machine.  It is located at /home/user/.virtualbox/machines/[machine name].  When you find the xml file, delete it (or you can delete the directory).  Then, create a new virtual machine.  While going through the steps, select the hard disk of the XP machine.  You will have to re-create your machine settings, but that should not be too hard.  

I can write in more detail tonight.  I do not have Virtualbox in front of me right now....

Offline Cressida

  • Sr. Member
  • ****
  • Posts: 283
Re: Had to change CPU and now cannot open my VM
« Reply #4 on: February 10, 2011, 03:11:18 PM »
^

I followed GermanTux instructions and that seems to have done the trick.  Thanks for the great suggestions
AMD Athlon 64 3200, 2GB ram,  ~320 GB HD,  Video=ATI Radeon X300 SE (128mb) PCI-e
KDE     Kern  3.2.18-pclos2.a64

I used to think I knew a lot about computers until I started using Linux.  Now I feel my age...

Offline GermanTux

  • Hero Member
  • *****
  • Posts: 693
Re: [SOLVED] Had to change CPU and now cannot open my VM
« Reply #5 on: February 11, 2011, 01:54:52 PM »
Glad to hear!  My apologies for posting the wrong paths by one folder :-p