Ticket #2699 (closed defect: fixed)

Opened 9 years ago

Last modified 8 years ago

Locked VDI or invalid type which is it ?

Reported by: Steve Richards Owned by:
Priority: major Component: virtual disk
Version: VirtualBox 2.0.6 Keywords:
Cc: Guest type: other
Host type: Linux


I have a VDI that can not be used. When I try to start the VM I get an error message that says

"PIIX3 cannot attach drive to the Primary Master. VBox status code: -3203 (VERR_VDI_INVALID_TYPE).

Result Code: NS_ERROR_FAILURE (0x80004005) Component: Console Interface: IConsole {e3c6d4a1-a935-47ca-b16d-f9e9c496e53e}"

When I try to clone the same VDI I get

"VirtualBox Command Line Management Interface Version 2.0.6 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved.

[!] FAILED calling virtualBox->OpenVirtualDiskImage(Bstr(argv[0]), vdi.asOutParam()) at line 3460! [!] Primary RC = NS_ERROR_FAILURE (0x80004005) - Operation failed [!] Full error info present: true , basic error info present: true [!] Result Code = NS_ERROR_FAILURE (0x80004005) - Operation failed [!] Text = Could not access hard disk image '/mnt/vm_drives/virtualbox/OS2_cics/OS2_cics.vdi' (VERR_FILE_LOCK_VIOLATION) [!] Component = HardDisk, Interface: IHardDisk, {fd443ec1-000f-4f5b-9282-d72760a66916} [!] Callee = IVirtualBox, {557a07bc-e6ae-4520-a361-4a8493199137} "

So I am confused. Which is the real issue ?

FWIW the VM was running as setup, and then there was a system reboot and it would no longer start. I have a copy of the VDI that I made prior to the crash and have replaced the VDI that was active at the crash and I receive the same error.

I can't really see any problems with a hanging lock, but I'm not sure where I would find it.

Thanks so much.

Change History

comment:1 Changed 8 years ago by frank

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

Please reopen if still relevant.

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