Open edwinvanrijn1 opened 6 years ago
The bus error is a pretty serious problem with the virtual machine itself. I would first suggest trying 'vagrant destroy' and running 'vagrant up' again, but also wonder if it's something fundamental about the amount of RAM the VM is requesting, or disk space.
The subsequent errors seem to happen with file writes which also makes me suspect the virtual disk created by VirtualBox has something fundamental wrong, so would also check disk space to make sure there was enough room for it to be created. I looked at my VM and it's virtual disk seems to be 30 GB (that's rather big!) but not only that, there is no provision in the Vagrantfile for setting or limiting the virtual disk size, it seems to come from the base VM image ubuntu/trusty64
. Maybe we should warn people the system requires at least this much free space to store the virtual disk!
Lastly (this is just a tiny issue) the latest/greatest version of the VM should be coming from the srvk/DiarizationVM repository, not this one (aclew/DiViMe) though it has no changes that would have resulted in the errors we see here.
Where the error 'read only file system' first appears, that happened because there was a file I/O error and so the filesystem was remounted read-only. Everything after that is noise because of no longer being able to write files :-/
Hello readers,
As I am installing vagrant on my Macbook Pro 2011 (2,4 GHz Intel Core i5, 4GB 1333 MHz DDR3) with OSX High Sierra 10.13.3. Nearly 70 GB storage left on a 160 SATA disk.
Even after following the instructions on the page and in other issues, I do not get it working. For these instructions I edited the Vagrantfile with
I included the log from where it went wrong: 'default: installing: libffi-3.0.13-0 ...' went okay but after that errors occur.
Thank you in advance!