virtualbox.org

MB Biostar H77MU3
•CPU i7-3770 LGA1155•4 ...DIMM DDR3 2GB 1600Mhz
•DVD 24X SATA DVDW
•VGA GeForce 9600GT 1024MB
•Win7 Home Prem 64 bit
•Pwr Antec 850W TP Quattro PS
•HD 2-WD 1tetra HD’s

VirtualBox version 4.3.6r9106

I can load and run Linux Mint 15 32 bit in VirtualBox and then surf, update Mint, add a new Wallpaper but after a couple hours Mint crashes. After the crash I can open and rub Ubuntu in VirtualBox but when I try to open Mint again I get the below info.

Failed to open a session for virtual machine Mint 15-32.
Failed to open image `C:
\Uers\xxxxx\VirtalBox VMs\Mint 15-32.vdi’
For writing due to wrong permissions
(VERR_VD_IMAGE_ONLY).
Failed to attach drive to Port0
((VERR_VD_IMAGE_ONLY).

__Details__________________________________________________
Result Code: E_FAIL (0x80004005)
Component: Console
Interface: Console {8ab7c520-2442-4b66-8d74-4ff1e195d22b6}


I removed and reinstalled Mint but the next day the same crash happened.

Any help would be much appreciated as I am using VirtualBox to learn Linux and am new to both Linux and VirtualBox.

Is that a verbatim error message? It looks wrong, and doesn't really make sense. It looks like it should say "VERR_VD_IMAGE_READ_ONLY" or similar, in which case the cause is self evident: your user don't have write access to the VM folder.

You are correct. I goofed copying it off of a snipped image. Why would it crash after running a couple hours and then have this problem?
I have two logs that are different. I am sorry I missed how to upload these yesterday.

rfharbin wrote:Why would it crash after running a couple hours and then have this problem?

The error message above can't happen 2 hours into a session. That error only happens when the VM is starting up: that's the only time when VDI files are being opened, so that's the only time you can get a file open error.

Are you missing out part of the story? Because I guess you might get the error if you tried to start a VM using VBoxManage on the command line, and the VM was already running.

I have not used VboxManage.
After it crashed I tried to open Mint again and that is when I received the message shown above. Maybe one of the two log files will help. I hope so.

The log file just repeats the error you originally reported.

Discard any saved state, make sure the image file is not write protected, and that your host user account has read/write access to the VM folder.

The .VirtualBox folder was read only although all the subfolders were properly set. Now all is well.

Many thanks! Very much appreciated.