id,summary,reporter,owner,description,type,status,component,version,resolution,keywords,cc,guest,host 13617,Startup fails if HDD image is immutable and not enough CPU power available,mskov,,"When HDD image is set to ""immutable"" and there is not enough CPU power available - VirtualBox crases with Fehlercode: VBOX_E_INVALID_OBJECT_STATE (0x80BB0007) Komponente: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913} The problem is independent of the guest type (startup with empty HDD images fails as well). I can always reproduce the problem when running a host with 1 CPU core without VT-x (don't know if the problem also occurs with VT-x). The problem occurs (at least) for VirtualBox 4.3.12 - 4.3.18 In the VBoxSVC.log one can find: ERROR [COM]: aRC=VBOX_E_INVALID_OBJECT_STATE (0x80bb0007) aIID={05f2bbb6-a3a6-4fb9-9b49-6d0dda7142ac} aComponent={Medium} aText={Medium 'C:\Users\trusteddisk\VirtualBox VMs\test\Snapshots/{402ef805-c1e2-4022-a4b1-65d3c194dd61}.vdi' is locked for writing by another task}, preserve=false So my guess is that the automatic resetting of the ""diff"" file for immutable images takes longer than it should if not enough CPU power is available and at the time of the actual startup the image is still being reset. ",defect,closed,other,VirtualBox 4.3.18,fixed,,,all,Windows