Why is Vagrant halt killing my VM?

Question

virtual box

Hello!
We have:

• Vagrant 2.2.6 with laravel/homestead 8.2.1
  
• VitrualBox 6.0.14
  
• macOS 10.13.6
  

After I close the created virtual box vagrant halt, and when I want to start it again vagrant up, I get the following error:

Your VM has become "inaccessible." Unfortunately, this is a critical error
with VirtualBox that Vagrant can not cleanly recover from. Please open VirtualBox
and clear out your inaccessible virtual machines or find a way to fix
them.

You have to delete the box from VirtualBox and the box folder from the directory, after that it vagrant upcreates a new clean one.
This is not very convenient, since you have to refill the database, perform migrations and all that.
Sometimes it starts normally, sometimes it doesn't - I haven't caught the pattern yet. At the same time, I do not make any edits inside the box.
Googled what I already did:

• Completely remove Vagrant and VitrualBox and reinstall them - did not help
  
• Clear index VBoxManage - did not help
  
• Rename homestead.vbox-prev to homestead.vbox replacing the existing one - did not help

Answer 1

Next time, take a look at the folder where this VM is located.
If the .vbox-tmp file is lying there after an unsuccessful shutdown, it means that VB simply for some reason could not replace the main .vbox with it - do it yourself.