Get rid of 64-bit Windows error since it should work now

This commit is contained in:
Mitchell Hashimoto 2011-12-22 12:50:47 -08:00
parent c42fe7ac6f
commit 3eede78876
2 changed files with 0 additions and 21 deletions

View File

@ -313,15 +313,6 @@ module Vagrant
error_key(:virtualbox_not_detected)
end
# Note that this is a subclass of VirtualBoxNotDetected, so developers
# who script Vagrant or use it as a library in any way can rescue from
# "VirtualBoxNotDetected" and catch both errors, which represent the
# same thing. This subclass simply has a specialized error message.
class VirtualBoxNotDetected_Win64 < VirtualBoxNotDetected
status_code(48)
error_key(:virtualbox_not_detected_win64)
end
class VMBaseMacNotSpecified < VagrantError
status_code(47)
error_key(:no_base_mac, "vagrant.actions.vm.match_mac")

View File

@ -153,18 +153,6 @@ en:
Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
this to be available on the PATH. If VirtualBox is installed, please find the
`VBoxManage` binary and add it to the PATH environmental variable.
virtualbox_not_detected_win64: |-
Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed
with version 4.0.0 or higher.
Additionally, it appears you're on 64-bit Windows. If this is the case, and
VirtualBox is properly installed with the correct version, then please make
sure you're running Vagrant via JRuby on a 64-bit Java runtime. For more
information on how to set this up and how to verify it is properly setup,
please view the guide online at:
http://vagrantup.com/docs/getting-started/setup/windows_x64.html
vm_creation_required: "VM must be created before running this command. Run `vagrant up` first."
vm_inaccessible: |-
Your VM has become "inaccessible." Unfortunately, this is a critical error