live snapshot broken, Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)

[ctr]

After upgrading to VirtualBox 4.1, I can no longer take snapshots of some virtual machines while they are running.

The VBox.log file attached is for a test with a Windows XP guest running on a Windows 7 x64 host.

(P.S. For a Fedora 14 guest running on the same host, taking a snapshot while running is taking ages to complete (>10 min so far) although there is not yet an error message.)

[Zium]

After upgrade to VirtualBox 4.1, if host memory is low VM crashes.

Host is Windows XP SP2, guest is ubuntu or Windows XP.

The VBox.2.log attached is for a Windows XP guest.

[ctr]

That Fedora 14 guest snapshot took > 1h (I went home), but this morning it had failed with an error VERR_SSM_TOO_MANY_PASSES. I am attaching the log file as VBox-Fedora14Guest.log.

[go3mon]

Trying to take snapshot on running guest RHEL6

[Tom]

Failure when attempting to snapshot a live VM (Ubuntu 11.04) on a Mac OS X Lion host

[Klaus Espenlaub]

This apparently is a generic breakage of taking live snapshots. It is actually unintentional that the GUI is capable of taking live snapshots (it should only take online snapshots for running VMs), however it is possible using the "Camera" icon in the snapshot tree view.

So the workaround is to avoid this way of taking snapshots of running VMs. Use only the menu item Machine->Take Snapshot... as this works reliably.

[phr33k]

The same problem appears when taking online snapshots via the VBoxManage snapshot command. Different VMs with Windows and Linux crashes. They all have the latest GuestAdditions installed. Hostsystem is a Debian Squeeze.

[bauner]

same error on ubuntu 11.04 64bit host with 32bit xp and s2k3 guests.

vboxmanage snapshot w2k3 take "snapshot vom $(date "+%Y-%m.%d %H:%m")" gives Guru Meditation -2701 error if the VM is running

for me snapshots working with menu machine -> Take Snapshot and with vboxmanage on paused vm vboxmanage snapshot w2k3 take "snapshot vom $(date "+%Y-%m.%d %H:%m")" --pause

[Frank Mehnert]

Correct, the --pause parameter is the proposed workaround.

[DHughes]

I have the same issue since upgrading to 4.1 I get a pop-up with: NS_ERROR_FAILURE (0x80004005)

[Frank Mehnert]

Zium, your problem is a duplicate of #9373.

[vega]

Is there any chanсe to get a fix?

[Frank Mehnert]

Yes, we are working on it but unfortunately it will take more time. I will get you informed when this issue is fixed.

[Robert Werner]

Seeing this issue also with Win 7 guest on 50GB dynamic HD, running on Fedora 15 host. Version 4.1.4. Strikingly, Save State works fine for a Win XP guest on a 20 GB dynamic disk on the same linux host.

[Guy Boyd]

Same issue with an Ubuntu 10.04 server guest on an Ubuntu 10.04 server host. The guest works fine on other similarly configured hosts, it seems to occur only on this one machine.

[chrulri]

Still not working in 4.1.6

[Edward Muller]

I am experiencing this error as well. Really frustrating because I was able to do snapshots just fine while building the base image that I'm using. But now that I'm using a copy of that image it bombs.

[ox11]

unfortunately still there in 4.1.8

[si458]

is this still an on going issue?

im having no problems with snapshots in 4.1.12 (Host: server 2008 r2, Guest: Windows XP Pro)

and everytime i try to take a snapshot using the phpvirtualbox, it wont let me because of this ongoing issue

[icemanoich]

Still not working in 4.1.14. Ubuntu 11.10 as a host and Ubuntu 10.10 as a guest. Work only if I safe state of VM (auto power off) and then I can take snapshot.

When this bug will be fixed?

[Frank Mehnert]

Replying to icemanoich:

Still not working in 4.1.14. Ubuntu 11.10 as a host and Ubuntu 10.10 as a guest. Work only if I safe state of VM (auto power off) and then I can take snapshot.

That's not true. It should be sufficient if you pause the VM (VBoxManage snapshot VM_NAME take SNAPSHOT_NAME --pause. If the VM is not paused then this is a live snapshot, which does not work, but taking a snapshot from a paused VM should work (and it works here).

We will eventually fix the live snapshot problem but currently there are other higher-priority items.