Frank
Thank you for the quick reply
On Wednesday 13 August 2008 16:23:50 Frank Mehnert wrote:
> On Wednesday 13 August 2008, paul williamson wrote:
> > I have been using 1.5.2 for some time now on my Evesham laptop, running
> > openSuse 10.3 as host and Windows XP as guest.
> >
> > I initially had some problems a few weeks ago, trying to update to 1.6.2.
> > That appeared to work fine. but I had the problem that it would not
> > re-start a machine after I had chosen "save the machine state" from the
> > shutdown menu.
> >
> > I tried today to upgrade to 1.6.4, and I couldn't get any of my .vdi
> > files to run at all. They appeared to start loading, then I got a screen
> > saying the I had changed hardware, and to try re-booting in safe mode, or
> > last known good configuration etc.
> >
> > I also tried 1.6.2. again today and had the same problem.
>
> Please change the IDE controller from PIIX4 to PIIX3 in the VM settings.
> Until VBox 1.5 the IDE controller type was set to PIIX3 by default,
> starting with VBox 1.6 we used the PIIX4 as default. However, it should
> not happen that VMs which were already created change the PIIX type, so
> this is probably a bug which we have to fix.
Thank you for that information. I have now got my .vdi from 1.5.2. running in
1.6.4.
> > I seem to remember that I should have seen a screen asking me to save, or
> > backup and save, some new settings. I saw that before when I tried
> > 1.6.2, but didn't see it today.
>
> This will only happen if you upgrade from 1.5 to 1.6.x.
Thanks - that explains the missing screens, as I have been re-naming my
VirtualBox folder in /home/paul, which is why I did not see the screen. I
just did an installation of 1.6.4. without doing that, and did indeed see the
screen.
> > I also have another hard-drive for this laptop on which I have installed
> > openSuse 11.0. I had identical problems when I tried to run 1.6.4. on
> > that yesterday. I eventually managed to get it to boot a .vdi using
> > "last known good configuration", but here as well it would not let me
> > re-start a machine after using "save the machine state".
>
> Same here, this is a VM setting which must fit your guest.
Sorry, but this is the point I don't understand. All the time I used 1.5.2, I
had no problems at all re-starting a "saved" machine. However, in 1.6.2 and
1.6.4, I have failed to do that, getting instead this error message:
"Unable to restore the virtual machine's saved state
from '/home/paul/.VirtualBox/Machines/Windows
XP/Snapshots/{f711b6c0-67e1-4d62-e999-3a1e83dfd6ad}.sav'. It may be damaged
or from an older version of VirtualBox. Please discard the saved state before
starting the virtual machine.
VBox status code: -1825 (VERR_SSM_LOAD_CONFIG_MISMATCH)."
I had this problem with 1.6.2 even after a full re-install of XP as the guest,
so it does not only happen when I transfer a .vdi from 1.5.2.
This feature is important for me, as I often have to re-start my laptop
several times a day in different locations, and being able to launch my
software quickly in VirtualBox has been very useful for me.
Are you saying that if I use a .vdi file from an earlier version of
VirtualBox, then there is no way that it will be able to re-start after
using "save the machine state" ? If so, then I will have to stay with 1.5.2,
as doing a full install of XP didn't solve the problem.
I know one other user of VirtualBox who has told me he has no problem
re-starting a saved machine after changing form 1.5.2 to 1.6.2. (Maybe he is
just lucky !)
Best wishes
Paul Williamson
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
