VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2161 - 2163 of 16363)

Ticket Resolution Summary Owner Reporter
#10556 obsolete Deleting snapshot gets suddenly interrupted + doesn't check for disk space + doesn't cleanup after fail matteo sisti sette
Description

There are at least 3 issues here, but since I don't know to which extent they are related, I report them together as they happened.

I'm sorry for the long report but this really NEEDS to be fixed because it is very, very critical

I had a VM with 2 snapshots (+ the current state), like this:

-+--Snapshot A

| +--+--Snapshot B

| +----Current State

From the guest's point of view, the VM's disk had a total space of 40GB of which 30 were used.

In the host, the original vdi file (corresponding to snapshot A) was about 8 GB in size, and the vdi file corresponding to snapshot B was about 22 GB in size. The vdi file corresponding to the current state I cannot tell, but it couldn't be very big because I hadn't written nor deleted much data since the last snapshot.

The machine was turned off.

  1. I deleted (or tried to delete) Snapshot B.

When the progress bar was at about 30%, the dialog with the progress bar suddenly disappeared, without an error message or anything. As if it had suddenly completed despite apparently being only at 30%.

Only that the snapshot was still there.

  1. In the hope that data had not been corrupted, I simply deleted the snapshot AGAIN. I forgot to check for disk space, but the VirtualBox Manager should, well, MUST check that enough disk space is available before starting such an operation. Here's the second issue

=> the host disk got full (it is about 50GB) during the snapshot deletion and the operation failed (V_ERR_DISKFULL or something like that). Available disk space should have been checked BEFORE starting the merge operation.

  1. After this failure, not one byte was cleaned up. The vdi file corresponding to the current state is now about 23 GB in size.

So I guess the merging is done in-place into the image belonging to the later snapshot.

After the disaster, I could boot the VM succesfully (which was a pleasant surprise), so I guess that even if the merging is done in-place it is done somehow in a safe way (this makes sense, otherwise you wouldn't do it in-place, would you?); but if so, then it should be possible, after such a failure, to clean up the garbage that has been left in the later differencing image.

(later I got an error when I tried to delete some files from the guest hard disk, because the host disk was full and I didn't realise that having differencing images, deleting was actually adding more data)

Unless the differencing image actually _is_ screwed up, just not enough to prevent the VM from booting?

#10561 obsolete Virtual machine 's name illegible on VirtualBox Manager Teutates09
Description

I encountered a problem with all the name of the virtual machine. The list of this virtual machines on the VirtualBox Manager is illegible. All the name are troncated and so it is very difficult to read and choose a virtual machine.

This problem exist since VirtualBox 4 and if I upgrade VirtualBox on the last version number, this problem persist.

My guest type is Windows 7 64 bits on a laptop with a screen on 17" and a video card NVidia GTX 460M (1.5 Mo) but the video card driver is correct.

You can see this problem on the screen capture.

#10564 obsolete blue screen of death maDC0w
Description

after the latest version, i have been getting a random blue screen of death after a few minutes of use. the host os is win7 64 and the guest can be anything (i've had it happen on winxp pro as well as ubuntu of different versions 11 or 12). i could not get the entire error on the bsod, but it said something like "DRIVER_IRQL_NOT_LESS_EQUAL". logs attached.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy