Hi, tl;dr: on my Win7 box Vagrant doesn't get the output of the VBoxManage command, so breaks completely.
I installed Ruby 1.9.3, Vagrant 1.4.3 and VirtualBox 4.3.6-91406 on my
Win7-64bit computer.
VirtualBox works perfectly, and "vagrant init" properly creates a
VagrantFile.
But when I ran "vagrant up" it said the VirtualBox version is unsupported,
and suggested a version 4.3 (which I have).
So I uninstalled/re-installed both, switched to VirtualBox 4.3.4-91027,
upgraded to Ruby 2.0, but still got the same error message (full debug file
attached).
Down I went into the Vagrant code, and traced the issue to the call to
"VBoxManage --version" (Base.execute("--version")), which strangely returns
an empty result (then causes Vagrant to exit with version issue).
Yet manually running the same command in a command prompt returned the
version number.
So I monkey-patched meta.rb by hard-coding the VirtualBox version number
(meta.rb line 34 changed to '@version = "4.3"'), and it started working,
but then it blew up on set_mac_address...
Basically, it seems that NO output from ANY VBoxManage command gets
captured.
Neither Google nor StackExchange got me anywhere - am I the only one with
this issue? Anybody got any idea what the cause could be?
Xavier
--
You received this message because you are subscribed to the Google Groups
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
debug.log
Description: Binary data
