virtualbox-4.0_4.0.6-71344~Ubuntu~lucid_amd64 update problem

[artemis_f0wl]

When I started up VB this morning, I got the notice of the virtualbox-4.0_4.0.6-71344~Ubuntu~lucid_amd64 update, which I downloaded and installed. Once restarted, VB complained about "Oracle VM VirtualBox Extension Pack" which I installed as well. Upon starting the Windows guest (That I was just working on yesterday afternoon) I get to the Windows XP splash screen then the error (See attached screen shot) and this begins an endless reboot loop. I've changed the IDE controller from PIIX4 to PIIX3 and ICH6, none of which made a difference with the error. This system doesn't have AV or a backup agent running, and I'm really not sure how else to fix this.

Any insight or suggestions appreciated.

[frank]

Please attach a VBox.log file of such a VM session.

[artemis_f0wl]

Sorry for the delayed response, been overly busy and just now catching up. I have attached the log file as requested. Thanks in advance for any help in resolving this issue.

[frank]

First make sure to use the IDE controller type you used originally.

I don't see the real reason in this log but first you should fix the wrong shared folder (the path does not exist on the host). Just remove that shared folder from the VM settings. If this still does not help then boot your guest in safe mode and uninstall the VBox guest additions. If the VM now boots then try to install the 4.0.6 additions.

[artemis_f0wl]

Thanks again for the response. I removed the shared folders that were outdated and I also attempted to boot into safe mode as the changes made no difference to my problem. I have made sure the IDE controller is set to the original "PIIX3", but still I can not get the guest to boot which prevents me from being able to uninstall the VBox guest additions.

I have attached another log from today's attempts, but I am officially lost as to what happened! I have no idea how the update borked my guest when I was just working on it hours before, and now I'm loosing hope that it can be restored. I sincerely hope someone can help me understand what the malfunction is so that I can avoid it in the future- I use VBox too often to risk loosing data or having to waste time restoring/rebuilding machines as I fear I will eventually end up doing with this one.

If there are any other ideas, I'd appreciate your sharing. At this point I'm willing to do anything to get this taken care of.

[artemis_f0wl]

Just a bump in case anyone new comes along w/ some good information. I've resorted to creating a new VM, and I'm still kicking myself for not having snapshots of the messed up guest, but I would still really like to get this resolved or at very least understand WHY it happened.