"Could not access VDI" VERR_FILE_LOCK_VIOLATION af
Posted: 15. Jul 2008, 14:47
Hi everybody,
following setting is installed here:
- several Linux systems (Ubuntu v8.04.1 - hardy) with each of it running
- VirtualBox v1.5.6_OSE which is accessing a central NFS share with
- three virtual Windows XP machines (3x VDI) stored there.
Every user can now startup VirtualBox locally and after an optional warning that notes one or two machines are not available (depending on how many VMs are running by others), the user can startup the remaining free VM(s).
So far so good, but unfortunately one host system just crashed with its VirtualBox session opened and a Windows XP guest running inside... Now, this VDI is somehow marked as locked and can't be accessed anymore - even after deleting it from the virtual disk manager it can't be added again. Trying to access the VDI image results in:
or in the error: My Question is now, where is this lock state stored and can it somehow be released to access the VDI again? I wasn't able to find a VBoxManage option that deals with such a lock state...
Tanks in advance for any hint,
cheers,
Uwe
following setting is installed here:
- several Linux systems (Ubuntu v8.04.1 - hardy) with each of it running
- VirtualBox v1.5.6_OSE which is accessing a central NFS share with
- three virtual Windows XP machines (3x VDI) stored there.
Every user can now startup VirtualBox locally and after an optional warning that notes one or two machines are not available (depending on how many VMs are running by others), the user can startup the remaining free VM(s).
So far so good, but unfortunately one host system just crashed with its VirtualBox session opened and a Windows XP guest running inside... Now, this VDI is somehow marked as locked and can't be accessed anymore - even after deleting it from the virtual disk manager it can't be added again. Trying to access the VDI image results in:
Code: Select all
Could not access hard disk image '/auto/opt/virtualbox/VDI/10GB_WindowsXP_1.vdi' (VERR_FILE_LOCK_VIOLATION).
Fehlercode:
0x80004005
Komponente:
HardDisk
Interface:
IHardDisk {fd443ec1-000f-4f5b-9282-d72760a66916}
Callee:
IVirtualBox {76b25f3c-15d4-4785-a9d3-adc6a462beec}or in the error:
Code: Select all
# VBoxManage showvdiinfo /auto/opt/virtualbox/VDI/10GB_WindowsXP_1.vdi
VirtualBox Command Line Management Interface Version 1.5.6_OSE
(C) 2005-2008 innotek GmbH
All rights reserved.
[!] FAILED calling virtualBox->OpenHardDisk(filepath, hardDisk.asOutParam()) at line 5184!
[!] Primary RC = 0x80004005
[!] Full error info present: true , basic error info present: true
[!] Result Code = 0x80004005
[!] Text = Could not access hard disk image '/auto/opt/virtualbox/VDI/10GB_WindowsXP_1.vdi' (VERR_FILE_LOCK_VIOLATION)
[!] Component = HardDisk, Interface: IHardDisk, {fd443ec1-000f-4f5b-9282-d72760a66916}
[!] Callee = IVirtualBox, {76b25f3c-15d4-4785-a9d3-adc6a462beec}
Tanks in advance for any hint,
cheers,
Uwe