Can't restart on 4.2.16
Posted: 5. Aug 2013, 00:40
VB 4.2.16 r86992 on OSX Mountain Lion 10.8.4. The VM is Win7 Ultimate SP1.
Since upgrading to 4.2.16, I get the following error every time I quit VB, save state, and then re-start the VM after re-starting VB. I've done the usual, i.e. repaired disk permissions, re-installed VB (and the extension pack and the tools). Same error, every time I try to re-start the VM from a saved state.
The error message says:
Failed to open a session for the virtual machine Win7.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
The last three lines in the log file are:
!!Assertion Failed!!
00:00:05.411045 Expression: !VMCPU_FF_ISSET(pVCpu, VMCPU_FF_INTERRUPT_PIC)
00:00:05.411046 Location : /Users/vbox/tinderbox/4.2-mac-rel/src/VBox/VMM/VMMR3/PDM.cpp(902) int pdmR3LoadExec(VM*, SSMHANDLE*, uint32_t, uint32_t)
I saw another "can't start any VM" problem here, but my problem is just on a re-start. After the abort, I can re-start the VM (from boot) without problem. They just won't re-start.
The only change has been the upgrade of VB; I haven't done any Windows Updates since that upgrade.
Any ideas?
Since upgrading to 4.2.16, I get the following error every time I quit VB, save state, and then re-start the VM after re-starting VB. I've done the usual, i.e. repaired disk permissions, re-installed VB (and the extension pack and the tools). Same error, every time I try to re-start the VM from a saved state.
The error message says:
Failed to open a session for the virtual machine Win7.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
The last three lines in the log file are:
!!Assertion Failed!!
00:00:05.411045 Expression: !VMCPU_FF_ISSET(pVCpu, VMCPU_FF_INTERRUPT_PIC)
00:00:05.411046 Location : /Users/vbox/tinderbox/4.2-mac-rel/src/VBox/VMM/VMMR3/PDM.cpp(902) int pdmR3LoadExec(VM*, SSMHANDLE*, uint32_t, uint32_t)
I saw another "can't start any VM" problem here, but my problem is just on a re-start. After the abort, I can re-start the VM (from boot) without problem. They just won't re-start.
The only change has been the upgrade of VB; I haven't done any Windows Updates since that upgrade.
Any ideas?