Dexter Filmore wrote:
>> Do you
>> still have the release log (search for that
>> VERR_SSM_LOAD_CONFIG_MISMATCH error message in the files under
>> $HOME/.VirtualBox), or can you reproduce it?
>
> I email them to your account. For the future: 60k logs to the list ok?
OK, these were the relevent lines. Anyone who is familiar with SSM and
PGM care to comment?
Regards,
Michael
00:00:06.795 Changing the VM state from 'CREATING' to 'CREATED'.
00:00:06.814 Changing the VM state from 'CREATED' to 'LOADING'.
00:00:14.224 Ram range: fff80000-ffffffff 00080000 bytes bits
00:00:14.224 State : ffdff000-ffdfffff 00001000 bytes nobits
00:00:14.224 SSM: LoadExec failed with rc=VERR_SSM_LOAD_CONFIG_MISMATCH
for unit
'pgm'!
00:00:14.239 Changing the VM state from 'LOADING' to 'LOAD_FAILURE'.
00:00:14.252 ERROR [COM]: rc=0x80004005
IID={1dea5c4b-0753-4193-b909-22330f64ec4
5} component={Console} text={Failed to restore VM state from
'/mnt/vm/vbox/winxp
sp2nowga/snapshots/{9da12f9c-92fe-486d-9e73-ffe501f26533}.sav'
(VERR_SSM_LOAD_CO
NFIG_MISMATCH).
00:00:14.252 VBox status code: -1825 (VERR_SSM_LOAD_CONFIG_MISMATCH)}
00:00:14.252 ****************** Guest state at power off ******************
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
