Funnily enough I just stumbled upon the solution to the problem referenced below (guests fail to start from saved state after an Virtualbox upgrade).
Simply enough: Discard the current state of the VM. You can now safely edit the network parameters to reflect the change in network adapter interfaces in Virtualbox. Someone did reply to my first problem report to edit the network interfaces (which I initially thought of as a "duh!" type of response) but did not mention discarding the current saved state of the VM. I'll take that as a lack of experience with virtualbox on my part. -geoff --------------------------------- Geoff Galitz Blankenheim NRW, Germany http://www.galitz.org/ http://german-way.com/blog/ _____ From: Geoff Galitz [mailto:[email protected]] Sent: Donnerstag, 9. April 2009 12:25 To: '[email protected]' Cc: '[email protected]' Subject: guest fails to restore from saved state I upgraded to VirtualBox 2.2.0, apparently making the mistake of having some guests in a saved state at the time. Now at least one guest VM will not start. The error is attached as a graphic: What is the right way to resolve this? Do I need to downgrade, shutdown the guests and then upgrade again? -geoff --------------------------------- Geoff Galitz Blankenheim NRW, Germany http://www.galitz.org/ http://german-way.com/blog/
<<image001.jpg>>
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
