You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After guest machine reloading (or halt => up) persistent storage fails to mount anymore and therefore guest OS fails to start. Vagrant freezes on vagrant up command and directly loading via virtualBox freezes as well.
Host system: os x 10.14.4.
VirtualBox 6.0.4 (with latest 5 version the same issue).
Vagrant version: 2.2.4
vagrant-persistent-storage version: 0.0.45
Guest box: generic/debian9 (version 1.9.8)
Vagrantile
vagrant up --no-provision (everything is ok, guest additions are installed, storage is also created and attached - I can see it on logging into machine)
vagrant reload (machine is not loaded anymore).
This reproduces for me each time.
This is what I see in guest system when connect to it via virtualBox:
The text was updated successfully, but these errors were encountered:
I am not sure which causes exactly the issue. To fix after first login I edited file /etc/fstab on guest and commented the last line there: /dev/persistent/persistent /persistent/ ext4 defaults 0 0. But I am still not sure what to do about this.
After guest machine reloading (or halt => up) persistent storage fails to mount anymore and therefore guest OS fails to start. Vagrant freezes on
vagrant up
command and directly loading via virtualBox freezes as well.Host system: os x 10.14.4.
VirtualBox 6.0.4 (with latest 5 version the same issue).
Vagrant version: 2.2.4
vagrant-persistent-storage version: 0.0.45
Guest box: generic/debian9 (version 1.9.8)
Vagrantile
How to reproduce:
vagrant up --no-provision
(everything is ok, guest additions are installed, storage is also created and attached - I can see it on logging into machine)vagrant reload
(machine is not loaded anymore).This reproduces for me each time.
This is what I see in guest system when connect to it via virtualBox:
The text was updated successfully, but these errors were encountered: