I. Description of the problem
1. droid4x restore snapshots can be restored by VirtualBox first
2. VirtualBox after restoring a snapshot if it is not started and shut down with VirtualBoxinstead of starting droid4x directly, the droid4x boot will error cmd: "C:\Program files\oracle\virtualbox\vboxmanage.exe" MODIFYVM droid4x--hwvirtex onResult:VBoxManage.exe:error:The Machine isn't mutable (state is Saved)VBoxManage.exe:error:Details:code vbox_e_invalid_vm_state (0x80bb0002), Component Sessionmachine, Interface Imachine, callee IUnknownVBoxManage.exe:error:Context: "sethwvirtexproperty(hwvirtexpropertytype_enabled, VALUEUNION.F)" at Line 633 of File VBoxManageModifyVM.cpp This is because droid4x will execute C:\Program files\oracle\virtualbox\vboxmanage.exe "MODIFYVM droid4x--hwvirtex on when booting Command VirtualBox in snapshot state will cause the command execution to fail
two. the right approach 1. Restore the snapshot first2. Start the snapshot with VirtualBox3. Close VirtualBox Precautions
:after testing, starting and closing too fast will cause VirtualBox to crash, so you should add a certain interval
This method is also applicable to the simulator based on the X86 image adaptation.
From for notes (Wiz)
droid4x Snapshot Restore