CPU upgrade and VM won't start

[Adrian Ban]

Hi,

I have a problem with CPU upgrading and VMs. After I've upgraded the CPU from Athlon II X4 645 to FX-8120 the VBoxManager given to this error:

VBoxManage: error: cpum#1: X86_CPUID_AMD_FEATURE_EDX_3DNOW_EX is not supported by the host but has already exposed to the guest [ver=12 pass=final] (VERR_SSM_LOAD_CPUID_MISMATCH)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole, callee

I've had to put my old CPU (Athlon) to start my VMs. There is a solution for this?

Best regards.

[Martin]

Did you shut down the guests completely?
You shouldn't change CPUs when the guest is just in a saved state (would be the same as trying it on a "real" PC in sleep mode).

[Adrian Ban]

Hi,

Hm .. I didn't thought about this. I'm using the vboxinit script. I've took a look into it and here is the command on stop:

stop()
{
# vms are saved, instead of stopped.
MACHINES=$($su_command "VBoxManage list runningvms | awk '{ print \$NF }' | sed -e 's/[{}]//g'")
for UUID in $MACHINES; do
echo "$0: saving machine ${UUID} state"
$su_command "VBoxManage controlvm $UUID savestate" >>/var/log/vb.log
done

}

And yes indeed:

root@Cacti:~# uptime
01:54:21 up 59 days, 5:00, 1 user, load average: 0.68, 0.67, 0.73
root@Cacti:~#

It puts the VM save state. Thanks for the tip.