Vagrant broken on Windows 64-bit

[edmellum]

I saw this had been discussed on IRC, but I thought I'd make an official issue of it so people can see it's being worked on.

Every Vagrant command I try is broken on Windows 64-bit. I'm running JRuby 1.6.4 (ruby-1.8.7-p330).

And of course here is the error I'm getting after a vagrant up:

ChildProcess::Error: Unknown error (Windows says "Operasjonen er utf\370rt.", but it did not.)
             handle_for at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/lib.rb:284
     windows_handle_for at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/jruby.rb:48
             handle_for at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/lib.rb:265
  std_stream_handle_for at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process_builder.rb:135
               setup_io at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process_builder.rb:105
                  start at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process_builder.rb:29
         launch_process at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process.rb:62
                  start at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/abstract_process.rb:62
                execute at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/util/subprocess.rb:56
                  chdir at org/jruby/RubyDir.java:335
                execute at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/util/subprocess.rb:55
                execute at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/util/subprocess.rb:20
                    raw at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/driver/virtualbox_base.rb:279
                   busy at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/util/busy.rb:19
                    raw at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/driver/virtualbox_base.rb:278
                execute at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/driver/virtualbox_base.rb:254
           read_version at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/driver/virtualbox.rb:117
             initialize at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/driver/virtualbox.rb:36
                reload! at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/vm.rb:129
             initialize at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/vm.rb:35
              load_vms! at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/environment.rb:426
                   each at org/jruby/RubyArray.java:1603
              load_vms! at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/environment.rb:425
                    vms at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/environment.rb:114
               multivm? at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/environment.rb:147
            vms_ordered at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/environment.rb:122
        with_target_vms at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/command/base.rb:88
                execute at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/command/up.rb:39
                execute at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/cli.rb:38
                    cli at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/lib/vagrant/environment.rb:156
                 (root) at c:/jruby-1.6.4/lib/ruby/gems/1.8/gems/vagrant-0.9.1/bin/vagrant:43
                   load at org/jruby/RubyKernel.java:1063
                 (root) at c:\jruby-1.6.4\bin\vagrant:19

For extra Google juice the error reported on IRC was the following:

ChildProcess::Error: Unknown error (Windows says "The operation completed successfully.", but it did not.)
             handle_for at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/lib.rb:284
     windows_handle_for at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/jruby.rb:48
             handle_for at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/lib.rb:265
  std_stream_handle_for at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process_builder.rb:135
               setup_io at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process_builder.rb:105
                  start at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process_builder.rb:29
         launch_process at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/windows/process.rb:62
                  start at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/childprocess-0.3.0/lib/childprocess/abstract_process.rb:62
                execute at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/util/subprocess.rb:56
                  chdir at org/jruby/RubyDir.java:447
                execute at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/util/subprocess.rb:55
                execute at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/util/subprocess.rb:20
                    raw at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox_base.rb:279
                   busy at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/util/busy.rb:19
                    raw at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox_base.rb:278
                execute at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox_base.rb:254
           read_version at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox.rb:117
             initialize at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/driver/virtualbox.rb:36
                reload! at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/vm.rb:129
             initialize at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/vm.rb:35
              load_vms! at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/environment.rb:426
                   each at org/jruby/RubyArray.java:1612
              load_vms! at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/environment.rb:425
                    vms at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/environment.rb:114
               multivm? at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/environment.rb:147
            vms_ordered at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/environment.rb:122
        with_target_vms at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/command/base.rb:88
                execute at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/command/up.rb:39
                execute at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/cli.rb:38
                    cli at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/lib/vagrant/environment.rb:156
                 (root) at c:/jruby-1.6.5.1/lib/ruby/gems/1.8/gems/vagrant-0.9.0/bin/vagrant:43
                   load at org/jruby/RubyKernel.java:1063
                 (root) at c:\jruby-1.6.5.1\bin\vagrant:19

[mitchellh]

I've reported the issue upstream to ChildProcess, since I don't have any way to fix this on my end, I believe: enkessler/childprocess#28

For now, 64-bit Windows users can use the RubyInstaller installation of Ruby fine.