For the very first time I tried the "save machine state" in Sun 
VirtualBox last week.  This morning I confidently went to open my 
Windows virtual machine to peek at some past invoices.  I got a little 
dialog that reported that VirtualBox was "restoring machine state".  It 
duly got to 99% -- then my machine reset, suddenly and without giving 
Linux a chance to do anything at all.  Fortunately I didn't have 
anything else running, at least in user space, in either the Windows 
virtual machine or on my Linux box.

Being stubborn, I tried it again.  Same deal.

Fortunately again, Sun gives you a way to discard the state of the 
virtual machine ("warning this is just like giving the virtual machine a 
hard reset" says Sun -- "well good!", thinks I), and doing so retrieved 
things to the point where I can get my accounting done.

Is this a known problem?  The obvious work-around is "don't do that", 
but I'm wondering if there's anything I could do differently to make it 
all better.

The only thing I can think of that may be unusual is that the virtual 
machine was created under the GPL version, but I'm now running Sun's 
free binary so I can get access to the USB ports.

TIA

-- 
Tim Wescott
Wescott Design Services
Voice: 503-631-7815
Cell:  503-349-8432
http://www.wescottdesign.com


_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug

Reply via email to