Paul, On Monday 05 January 2009, paul williamson wrote: > I am using VB 2.1.0 - the "full" version (with USB support). > I create the old VM state by going to the "machine" menu/close - then > select the top option "save the machine state". (Or by using the Host > Key/Q to get to the same shutdown menu). > > Yes, I can "discard" the machine state and re-start it, but that negates > the whole purpose of "saving" the state in the first instance. > > I take my laptop into several different places each day, and each time I > have to open my VB/XP guest OS. I value the amount of time saved by being > able to "save" and "restore" instead of having to shutdown and "reboot" the > guest OS. > > As I said, I have noticed that this behaviour only happens with the more > recent versions of VB, and only when the host OS is installed on a SATA > hard drive. I had no problems when my host OS was on an IDE drive (on my > desktop PC), but that option is not available on my laptops.
Ok, if that is really the case (you save the machine state of a VM and restore it with the same version of VirtuallBox) then this is indeed a bug. Please could you open a bug report at www.virtualbox.org and attach two VBox.log files: The first log file from the VM session after you closed the VM by saving the state, the second log file from the other VM session when you tried to start that saved VM. Kind regards, Frank -- Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
