Instability with new version 4.1.8

[armagedon51]

I upgrade successfully Virtualbox with the new version 4.1.8. I have 3 VMs ; XP, Vista and 7. When I tried to update the addons to the Vista VM, the machine start crashing after the reboot. I restore a snapshot and tried again, same result. Now I lost the machine as VB put the message "cannot open hard disk UID ". So I guess it is lost for good. I then tried to ugrade XP, after the reboot, same thing, it crash after reboot to. Now, even Virtual Box start crashing again. Only W7 seems to be running after the update. Now what the hell was in that release as it screw up the entire program and my Vms ?

Asus A8NE
Opteron 180
2.5 GB DDr2 ram
Nvidia GT8800

[atmanning]

I too encountered a stability problem with 4.1.8 hosted under Ubuntu 11.10

I foolishly started a snapshot on a running Windows 2008 server.
I had the OS installed along with guest additions, and thought I would try out a snapshot, not thinking that I should shut it down first.

I lost all connections to both the guest 2008 server and to the *hosting server* itself (VNC session).
I had to walk over to the lab to access the hosting server console. The host system did not appear to have rebooted. Virtualbox now will not start the w2008 guest.

Attempt to access the guest shows that it is inaccessible due to a problem with disk 'differencing'
Attempt to create a new guest using the old .vdi file results in error about this .vdi being unavailable.

Now I will re-install my test server, moving a bit more cautiously this time.
Using a fixed (30 Gig) disk instead of dynamic for better performance on this circa 2005 blade server - HP Proliant DL380 - dual core 12 Gig of Memory.

[02walshe]

Oh dear; it looks like mine isn't an isolated incident

I've upgraded to V4.1.8 on a Windows XP Professional host, which has been running VM's fine before I've upgraded. I mostly virtualise Windows Server 2003 Enterprise and Ubuntu Server (as I build VM's on my workstation before moving them onto my hosting server).

My first action after the upgrade was to create a new VM and install a copy of Windows Server 2003 Enterprise (from the same ISO that I've used before without issue). Interestingly enough this is the first VM I've decided to use snapshots on in VirtualBox. It keeps crashing on two points: when logging in after the reboot needed to install the guest additions, or during the installation of SP2. This is on the initial desktop you get just after completing the installation of the OS. Each time it crashes, I went back a snapshot and tried again, but it keeps crashing.

I'm going to try installing the OS on a new VM without snapshots and see if it does the same thing. Would be appreciative if anyone else has any ideas to the problem though...

Thanks,
02walshe

[atmanning]

I solved my problem without as much a problem as I thought, although the machine disconnect is still a mystery.

I had installed version 4.1.8 extension pack on a 4.1.2 version (installed via apt-get install virtualbox in Ubuntu 11.10 host).
After manually downloading the 4.1.8 version, I was able to access my old system I thought had become corrupted after the crash.

It should have complained about the version difference in the extension!
I had also installed the version 4.1.8 guest additions.

Things seem to be ok for me now... still testing