System Snapshot crashing VM | TurnKey GNU/Linux

Hi guys,

everytime I take a system snapshot the VM crashes and displays aborted state.

Anyone knows why this happens? Im using the wordpress appliance in virtualbox.

One thing, I have to delete de snapshot in order to make the VM bootable again, I can also export the appliance and import it under a different name and everything works. Pretty weird issue if you ask me...

thanks in advance for any help you can provide.

If you need a log or anything just ask.

Replies (7)

Haven't experienced that one.

Reply 1 2011-02-15

I often run TKL appliances within VBox (v3.2.8 running on Ubuntu 10.04) and have never experienced that problem. Not sure which version you are using but perhaps its a VBox bug?

Have you tried with Ubuntu 10.04.1 server

Reply 2 2011-02-15

It may be worth trying with Ubuntu server, may help locate the source of the issue.

VirtualBox version

Reply 3 2011-02-15

Forgot that! Running VirtualBox 4.x (cant remember the exact version but I will update it tomorrow). My host OS is Archlinux with gnome DE

Yeah was thinking try Ubuntu 10.04 server in a new VM

Reply 4 2011-02-15

But perhaps try updating VBox first, like you said. I notice that Oracle now supply pre-built packages and have both .deb & .rpm repos so that should be pretty easy.

Possible crash of VMDK image

Reply 5 2011-02-15

You mean install a new VM in virtualbox with ubuntu server on it and try?

Will do and come back with results, also, Virtualbox version is 4.0.0 and just read the changelog for the new version (4.0.2) and this got my attention:

Storage: fixed possible crashes with VMDK/VHD images with snapshots and async I/O (4.0 regression)

The virtual disk is indeed an VMDK image, but I didnt get any I/O errors on the log. I think that is closely related to the issue, first thing I will do is update VirtualBox and if that doesnt make the trick then install an ubuntu server guest and see if problem occurs again.

Excellent

Reply 6 2011-02-16

Thanks for posting back.

Fixed

Reply 7 2011-02-16

As the changelog stated, it was a bug, working perfectly now after update :D

So in short, dont use VirtualBox 4.0.0, update inmediatly to 4.0.2