Opened 13 years ago
Closed 11 years ago
#9255 closed defect (fixed)
live snapshot broken, Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION)
Reported by: | ctr | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 4.1.4 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Windows |
Description (last modified by )
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.)
Attachments (5)
Change History (33)
by , 13 years ago
by , 13 years ago
Attachment: | VBox.2.log added |
---|
comment:1 by , 13 years ago
comment:2 by , 13 years ago
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.
by , 13 years ago
Attachment: | VBox-Fedora14Guest.log added |
---|
by , 13 years ago
Attachment: | VBox.3.log added |
---|
Failure when attempting to snapshot a live VM (Ubuntu 11.04) on a Mac OS X Lion host
comment:3 by , 13 years ago
Guest type: | Windows → other |
---|---|
Summary: | Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) with a Windows XP guest in a Windows 7 x64 host → live snapshot broken, Guru Meditation -2701 (VERR_VMM_RING0_ASSERTION) |
comment:4 by , 13 years ago
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.
comment:5 by , 13 years ago
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.
comment:6 by , 13 years ago
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
comment:8 by , 13 years ago
I have the same issue since upgrading to 4.1 I get a pop-up with: NS_ERROR_FAILURE (0x80004005)
comment:11 by , 13 years ago
Version: | VirtualBox 4.1.0 → VirtualBox 4.1.4 |
---|
Yes, we are working on it but unfortunately it will take more time. I will get you informed when this issue is fixed.
comment:12 by , 13 years ago
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.
comment:13 by , 13 years ago
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.
comment:15 by , 13 years ago
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.
comment:17 by , 13 years ago
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
follow-up: 19 comment:18 by , 12 years ago
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?
comment:19 by , 12 years ago
Description: | modified (diff) |
---|
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.
comment:20 by , 12 years ago
If the real fix is difficult, please could you at least stop it from crashing the virtual machine if you forget to use --pause? E.g. refuse to take a snapshot if the system is running?
comment:21 by , 12 years ago
I just lost an hour of work because I thought that if a command was in vboxmanage it would work, rather than crashing the entire VM for no reason--how silly of me. If it doesn't work, REMOVE THE COMMAND!
What is a higher priority than DATA LOSS CRASH BUGS? What is so hard about disabling broken code??
follow-up: 23 comment:22 by , 12 years ago
still there with 4.2.0r80737, Ubuntu 12.04 64bit Host and 32bit Client. The Host has the extension pack installed (providing RDP etc.).
I used "VBox... snapshot ..." with the running VM.
So for 16 months there have been worse issues than this, preventing a fix? It seems I overestimated the stability dramatically.
comment:23 by , 12 years ago
to manually recover, I had to
- replace the new NAME.vbox with the old NAME.vbox-pre file
- edit this recovered NAME.vbox file to remove the line(s) Harddisk (ABC-123.vdi) created by the snapshot
- remove the Snapshots/ABC-123.vdi (may be optional, but it is confusing to leave it there)
comment:24 by , 12 years ago
I admit that this is an annoying behavior. We will work on that bug soon as there is customer demand but in the mean time it's indeed the right fix to disable that functionality until this bug is fixed. The workaround to pause the VM still works but I think we should always pause the VM, even if the user didn't specify that.
comment:25 by , 12 years ago
But, it is not just with running VMs. I have a similar problem with restoring an earlier snapshot and deleting an intervening one. I would end up with multiple Harddisk lines and a corrupt VM. This has also been a long running bug, although it has been happening less with more recent releases. However, it was impacting my testing environment to such an extent, that I have given up on using VirtualBox snapshots, and have, instead, started using btrfs filesystem snapshots.
comment:26 by , 11 years ago
Can I, as a customer, say that I have a demand for this?
I'm slightly surprised that working live snapshots is seeingly considered such an esoteric request!
Or maybe it's fixed, but you forgot about this thread?
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.