Opened 3 years ago
#20035 new defect
Cloned guest poweroff fails and causes complete VM lockup
| Reported by: | centurion | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 6.1.16 |
| Keywords: | VERR_VM_INVALID_VM_STATE | Cc: | |
| Guest type: | Windows | Host type: | all |
Description
While provisioning a Windows 2016 cloned guest machine using Vagrant, a reboot command is issued that causes the guest to become completely locked up. The vbox.log shows that this appears to be an issue with the state transition table:
00:01:39.652519 Console: Machine state changed to 'Stopping' 00:01:39.652837 Console::powerDown(): A request to power off the VM has been issued (mMachineState=Stopping, InUninit=0) 00:01:42.828602 AssertLogRel F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\PDMThread.cpp(990) int cdecl pdmR3ThreadSuspendAll(struct VM *): RT_SUCCESS(rc) 00:01:42.828631 PDMR3ThreadSuspend -> VERR_TIMEOUT for 'HOSTRES' 00:01:42.828642 PDMR3PowerOff: 60 136 616 676 ns run time 00:01:42.828649 Changing the VM state from 'POWERING_OFF' to 'OFF' 00:01:42.828685 VMR3PowerOff: 00:01:42.828693 RUNNING -> POWERING_OFF, SUSPENDED -> POWERING_OFF, DEBUGGING -> POWERING_OFF, LOAD_FAILURE -> POWERING_OFF, GURU_MEDITATION -> POWERING_OFF, FATAL_ERROR -> POWERING_OFF, CREATED -> POWERING_OFF, RUNNING_LS -> POWERING_OFF_LS, DEBUGGING_LS -> POWERING_OFF_LS, GURU_MEDITATION_LS -> POWERING_OFF_LS, FATAL_ERROR_LS -> POWERING_OFF_LS failed, because the VM state is actually OFF 00:01:42.828729 VMSetError: F:\tinderbox\win-6.1\src\VBox\VMM\VMMR3\VM.cpp(3338) int cdecl vmR3TrySetState(struct VM *,const char *,unsigned int,...); rc=VERR_VM_INVALID_VM_STATE 00:01:42.828857 VMSetError: VMR3PowerOff failed because the current VM state, OFF, was not found in the state transition table (old state FATAL_ERROR_LS) 00:01:42.830483 ERROR [COM]: aRC=VBOX_E_VM_ERROR (0x80bb0003) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Could not power off the machine. (Error: VERR_VM_INVALID_VM_STATE)}, preserve=false aResultDetail=-1907
The only way to recover from this is to kill the VM using task manager.
This issue is reproducible on both MacOS and Windows versions of VirtualBox and more information can be found here: https://github.com/clong/DetectionLab/issues/517
vbox.log