mitchellh/vagrant — Issue #670: v0.9+ w7 64 jruby The operation completed successfully., but it did not.
Author: npmap
Created: 2012-01-21 19:59:49+00:00
State: open

On windows 7 x64 with jruby 1.6.3 (jruby 1.6.5.1 does the same) and virtualbox 4.1:
vagrant up
ends up throwing this:
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

This happens when using an existing suspended, a halted and a fresh environment with vagrant.
The error is exactly the same in 0.9.1 and 0.9.2.