virtualbox.org

hey

I am using Windows 7 Home Premium. I have installed Virtualbox 4.1.8 on it and trying to use a VM Image to use Ubuntu as guest OS. I did everything as instructed but when i try to start the image there is an error that says

Failed to open a session for the virtual machine MyU.

Failed to open image 'C:\Users\someUser\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\4T6CY3EF\vm-0.8.0-0.8.1[1].vdi' for writing due to wrong permissions (VERR_VD_IMAGE_READ_ONLY).

Failed to attach driver below us! Image is read-only. (VERR_VD_IMAGE_READ_ONLY).

AHCI: Failed to attach drive to Port0 (VERR_VD_IMAGE_READ_ONLY).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}

'MyU' is the name of the VirtualOS
The account i am using has administrator privileges.
Do you need any more info?

Attached is the Virtual Box log file

thanks

The error message is self explanatory. What else do you need to know?

Creating a VM around a VDI which is located in a temporary files folder seems... very unwise. Instead, create a subfolder in your "VirtualBox VMs" folder, locate the VDI file there, and rename it to have a meaningful name. Since your user has access to that folder, that should stop any further permissions problem. You should also check that the file does not have the write protect flag set in its properties.

thanks

The VM file was a zip file and when i clicked it using VirtualBox Wizard it showed .vdi file so I used it without uncompressing it. That was the problem

I came across this issue this morning on Windows 7. I discovered the issue was our corporate backup solution trying to backup the .vdi file, and keeping a handle on it while doing so.
I stopped the backup process and the vdi started working again.
The same symptoms could also appear for anti-virus scanners I suspect, so to find out if something has a handle on the vdi file you can use Process Explorer's "Find Handle or dll" function and enter the name of the vdi file.

On Linux, you can use something like lsof to find the same thing. Hope this helps.

Thanks, that does offer a useful insight.... though there would have to be an additional step since a VM would not reference a VDI copy stored in a temp folder.