Vagrant VM setup for kitsune
Puppet Ruby
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
manifests Merge pull request #3 from berkerpeksag/patch-1 May 2, 2012
README.rst Fix formatting Nov 2, 2011
Vagrantfile Fix syntax and get loud Sep 20, 2011



Follow these steps to run a kitsune [1] development environment inside a virtual machine [2]


Clone the repository:

$ git clone git://
$ cd kitsune-vagrant

Then add a vagrant box [3]:

$ vagrant box add kitsune

Then up the vagrant box:

$ vagrant up

This will take about 15-20 minutes to run on a "modern" machine (author has 2.66Ghz Macbook Pro w/4GB RAM). When it finishes, you should be able to open:

Eventually, you will be able to see kitsune running by opening in your browser (via mod_wsgi).


  • Use instead of
    • XXX?
  • Add mod_wsgi support.


Vagrant is taking too long

Sometimes vagrant up will say:

[default] Waiting for VM to boot. This can take a few minutes.

then take much longer. If it takes longer than a few minutes, CTRL-C and re-run vagrant up.

Vagrant says read-only fs

Sometimes vagrant up will quit with the message:

[default] err: Could not send report: Got 1 failure(s) while initializing: change from absent to directory failed: Could not set 'directory on ensure: Read-only file system - /var/lib/puppet/rrd

vagrant destroy and vagrant up again should fix the problem (whatever it is).


[2]Requires vagrant and VirtualBox to be installed:,
[3]You only need to do this once. Afterward you can vagrant destroy and vagrant up as needed.