Vagrant: VBoxManage: error: Failed to load unit 'lsilogicscsi'

[utkonos]

Version: Vagrant 2.2.4
Provider: VirtualBox 6.0.4 r128413
Host: macOS 10.14.4
Guest: ubuntu/cosmic64 v20190404.0.0

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "ubuntu/cosmic64"
  config.vm.provision :shell, path: "bootstrap.sh"
end

bootstrap.sh

#!/usr/bin/env bash
echo "success"

Debug output

https://gist.github.com/utkonos/02307b22f9847ba952e7dbb8bf7056da

Expected behavior

VM snapshot should pop off the stack.

Actual behavior

Fails with error:
VBoxManage: error: Failed to load unit 'lsilogicscsi' (VERR_SSM_LOADED_TOO_LITTLE)
An identical error occurs when running vagrant snapshot restore

Steps to reproduce

$ vagrant up --no-provision
$ vagrant snapshot push
$ vagrant provision
$ vagrant snapshot pop

[briancain]

Hey there @utkonos - This to me looks like a virtualbox bug. Did you happen to upgrade VirtualBox after taking that snapshot at all? I recommend reading this thread, it seemed to have the solution:

https://forums.virtualbox.org/viewtopic.php?f=3&t=91192

And here's the virtualbox ticket:

https://www.virtualbox.org/ticket/18263

I _think_ there's a patched version of VirtualBox out too according to that ticket, but it looks to just be a "testbuild" instead of in an official release yet. Hopefully that fixes your issue!

Thanks!

[stanislaw]

I have exactly the same setup except that my guest is Ubuntu 64 Xenial.

This sometimes starts happening to my VM as well: I am doing a vagrant up command and seeing this message.

My current solution: vagrant reload reloads the machine and the error goes away.

[ttibensky]

@stanislaw thank you. your comment made me realise that I killed my VM in a non-proper way and than it wasn't able to start again. vagrant reload discards previous state and spins up the VM successfully

[cblicous]

Thanks with the vagrant reload, that helped me too

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.