Ticket #10627 (closed defect: obsolete)

Opened 6 years ago

Last modified 21 months ago

VERR_VD_IMAGE_READ_ONLY after VirtualBox hangs

Reported by: ycollet Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.16 Keywords:
Cc: Guest type: other
Host type: other



I use VirtualBox 4.1.16 on Windows XP 64 bits. My guest OS is mageia 2 64 bits. I started virtualbox and from time to time, virtualbox closes brutally some seconds after I started the mageia 2 disk. After that, I've got a VERR_VD_IMAGE_READ_ONLY error and I am not able to boot the image anymore. The solution I found is to clone the virtual disk and then everything starts again.


VBox.log Download (48.6 KB) - added by ycollet 6 years ago.

Change History

Changed 6 years ago by ycollet

comment:1 Changed 6 years ago by ycollet

I finally found the problem: Some kind of system process was currently accessing the vdi file. I used process explorer from microsoft. I used the "find handle" menu to find who was accessing the vdi file. It was some kind of "system process" (I don't know which one it was, but maybe it was some kind of antivirus because once I killed the handle, the system process accessed the next vdi file in my directory). But after killing the handle, virtualbox was able to boot my guest OS without having to clone the vdi file.

comment:2 Changed 21 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete

Please reopen if still relevant with a recent VirtualBox release.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use