VirtualBox

Opened 14 years ago

Closed 8 years ago

#8040 closed defect (fixed)

VirtualBox crashes when writing to a VHD disk

Reported by: Daniel Owned by:
Component: virtual disk Version: VirtualBox 4.0.0
Keywords: Cc:
Guest type: Windows Host type: Windows

Description (last modified by Frank Mehnert)

Host OS: Windows 7 x64 Guest OS: Windows 2008 R2 x64 standard

The error occurs whenever I try to install Windows 2008 r2 Standard guest virtual machine onto a dynamic .VHD file. As soon as there is access to the disk, VirtualBox crashes.

The .VHD file was created using the Microsoft "Disk Management" administrative tool that comes with Windows. It's a 80 GB dynamicly growing file, currently about 9 gigs in size.

Details of the error: A problem caused the program to stop working correctly. Please close the program.

Windows Event log Application Error (Event ID 1000): Faulting application name: VirtualBox.exe, version: 4.0.0.0, time stamp: 0x4d12068f Faulting module name: VBoxDDU.dll, version: 0.0.0.0, time stamp: 0x4d120676 Exception code: 0xc0000005 Fault offset: 0x0000000000006560 Faulting process id: 0x31c Faulting application start time: 0x01cbaf99fdbe6478 Faulting application path: C:\PROGRA~1\Oracle\VIRTUA~1\VirtualBox.exe Faulting module path: C:\PROGRA~1\Oracle\VIRTUA~1\VBoxDDU.dll Report Id: 550fe08f-1b8d-11e0-9488-6cf049b76ab5

Attachments (3)

VBox.log (41.1 KB ) - added by Daniel 14 years ago.
windows event id 1000.txt (488 bytes ) - added by Daniel 14 years ago.
windows event id 1000 (VBox 4.1.10.0).txt (1.7 KB ) - added by landrey 13 years ago.

Download all attachments as: .zip

Change History (12)

by Daniel, 14 years ago

Attachment: VBox.log added

by Daniel, 14 years ago

Attachment: windows event id 1000.txt added

comment:1 by aeichner, 14 years ago

I'm not able to reproduce the crash. Could be fixed in the next maintenance release (see #7947) though you are not using any snapshots. Would be great if you could try again with the next maintenance release and report back. The bug can be avoided if you enable "Use host I/O cache" in the storage controller settings.

comment:2 by Daniel, 14 years ago

Yes, enabling "Use host I/O cache" does the trick! It works now!

Thanks!!

comment:3 by Frank Mehnert, 14 years ago

Resolution: fixed
Status: newclosed

Please reopen if still reproducible with VBox 4.0.2.

comment:4 by landrey, 13 years ago

Resolution: fixed
Status: closedreopened

Hi,

I've found the same issue in VBox 4.1.10.0 The bug was very reproducible in VM with CentOS 6.2 64bit. The VM had dynamic virtual disk in VHD format with size = 76G. Also that VDisk was configured to work in write through mode.

Looks like switching controller to "Use host I/O cache" mode fixes it.

Andrey

comment:5 by Frank Mehnert, 12 years ago

Description: modified (diff)
Resolution: fixed
Status: reopenedclosed

There were more VHD fixes in the meantime. Please reopen if still relevant with VBox 4.2.10.

comment:6 by doveman, 10 years ago

Still happens here with Vbox 4.3.12 on Win8 x64 with a Win7 x86 VHD unless I tick "Use host I/O cache"

comment:7 by doveman, 10 years ago

Resolution: fixed
Status: closedreopened

comment:8 by Klaus Espenlaub, 10 years ago

I strongly suspect that the issue you're running into has been fixed in 4.3.16, see Changelog. I guess that the VHD file you're using has been created with some other product and later used with VirtualBox.

Of course only you can ultimately tell if it's really fixed - but 4.3.12 is getting old and you should update (if there are trouble updating, let us know either in the corresponding forum or in one of the related existing tickets).

comment:9 by aeichner, 8 years ago

Resolution: fixed
Status: reopenedclosed

Closing as fixed, please reopen if still relevant.

Note: See TracTickets for help on using tickets.

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