-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin does not work w/ Vagrant >= 1.1.x #2
Comments
Sounds like a pretty cool plugin! Any plans on making it compatible to Vagrant 1.2? |
I'll see what I can do. |
I think this involves making it compatible with embedded ruby project, rights? |
I have a (mostly) working modification of this working under vagrant 1.2.3 - in my fork .. it could do with some testing before I submit a pull request. Would anyone like to help with some testing? |
Hi there - does it also work using the latest Vagrant version? I'd like to test it, but I'm always on the latest Vagrant version. |
Not sure, to be honest ... I could upgrade and test it on the latest, but I'm a little reluctant to, since I've got a few other plugins installed that are quite critical to my work, and I don't want to suddenly be unable to use those.. I guess you could try and see? I've been testing by symlinking my checkout to ~/.vagrant.d/gems/gems/vagrant-persistent-storage-0.0.2 It works on 1.2.3, so I'm assuming it will work on 1.2.7 (latest now, apparently) |
Caveats: it's currently dependent on the VirtualoBox provider, and has hooks that are particular to VBox... this should be fairly straightforward to get working for VMWare fusion, but I've not got that installed to test it.. and it means that the hooks will need to be made provider agnostic/independent. |
I'm on Windows but if you tell me how to install the gem I can test the plugin on the currect Vagrant version. |
you should be able to install it using the vagrant commandline switch: vagrant plugin install vagrant-persistent-storage this will install the version that's incompatible with the latest vagrant, but you can then remove the plugin and replace it from one cloned from my fork. I've not used vagrant or even ruby/gem on Windows before, so I'm a little in the dark about where the plugins are installed etc ... but in order to test the changes I've put in, you'll need to clone from git@github.com:madAndroid/vagrant-persistent-storage.git and then overwrite the original plugin install with the contents of that checkout/clone ... good luck! let me know how you get on.. really interested to see how this works on vagrant on Windows |
Okay, I'll have a look soon - just playing around with some packer building. :) |
hi @kusnier, would you be willing to accept a pull request to implement the vagrant > 1.1.x plugin compatibility? |
Yes. I will check first if the changes are working. |
great stuff :) cheers! |
I have tested your changes but something is not working right. The drive is not created and attached. How i tested: Created a checkout of your fork.
Fix Version in gemspec: Remove old vagrant dependency Create and install the gem:
Now create a new vagrant box: Add following to the Vagrantfile
vagrant up The log files can be found on gist: https://gist.github.com/kusnier/6434718 I have used a Mac (10.8.4) for my tests. |
ah, will need to update the README.md .. I had recently added an 'enabled' switch, here: https://github.com/madAndroid/vagrant-persistent-storage/blob/master/lib/vagrant-persistent-storage/config.rb#L35 can you add that to your config and try again? config.persistent_storage.enabled = 'true' perhaps that could be omitted and made implicit on the presence of the other config keys |
also, just tried with your config .. you'll need to ensure the storage size is quoted: "5000" |
looks like it's going to need more work .. I'll make some more changes when I get the chance, and ensure it's working properly.. |
With I found a other problem. When you do a
|
Okay, I've made some changes to address the disk being overwritten, it wasn't being created each time, but the scripts which format the disk were overwriting it, as far as I can tell. This was working okay on centos, but not on ubuntu - I've confirmed that it's working on ubuntu now. The issue with destroy: I wasn't experiencing that, I'm using Ubuntu; not sure if the hot swap capabilities of virtualbox are different between OSx and Linux. I'm assuming that;s the reason you were seeing that, but my testing didn't bring that up... I've adjusted the hooks here: could you please update from my fork again, and retest? thanks :) |
The drive is not accessible after a This are my steps for the test:
|
Hi, I've made a number of changes to address the issues you've discovered during your testing, @kusnier I've tested 'halt', 'suspend' and 'reload', in both an Ubuntu Precise and CentOS 6.4 Virtualbox VMs, on an Ubuntu host machine. Please could you run your tests again? thanks :) |
Tested, no problems found. Nice work! |
fantastic! thank you very much :D pull request coming right up ... |
Version 0.0.3 released. |
Uh ye, didn't have time but nice to see this fixed/merged! :) |
The following error can be found in the logs:
The text was updated successfully, but these errors were encountered: