`dvm up` hangs on VMFusion 6, missing OS about dvm HOT 4 OPEN

Yeah, I wish this were not still an issue--I take it you're running Vagrant 1.6.0 or later?

I have a tiny bit of background in an old blog post, but the only decent workaround I've settled on was to using version 1.5.4 of Vagrant with the VMware Fusion provider. The related issues are linked in the post.

Sorry this is still happening

from dvm.

@fnichol, I'm sort of working around the problem locally by using a modified snippet of the vmware config from the box's Vagrantfile in dvm's:

  ["vmware_fusion", "vmware_workstation"].each do |vmware|
    config.vm.provider vmware do |v, override|
      override.vm.box_url = "#{release_url}/boot2docker_vmware.box"

      # Copy config from box to work around config merging issue
      vagrant_home = ENV['VAGRANT_HOME'] || File.join(Dir.home, '.vagrant.d')
      v.vmx["bios.bootOrder"] = "CDROM,hdd"
      v.vmx["ide1:0.present"] = "TRUE"
      v.vmx["ide1:0.fileName"] = Dir.glob("#{vagrant_home}/boxes/boot2docker-#{b2d_version}/**/*vmware*/boot2docker-vagrant.iso").first
      v.vmx["ide1:0.deviceType"] = "cdrom-image"

      v.vmx["memsize"] = Integer(memory)
      v.vmx["numvcpus"] = Integer(cpus)
    end
  end

I'm happily running on Vagrant 1.6.3 with that modification. Perhaps it makes sense to make similar changes part of dvm?

from dvm.

At the risk of adding a "me too!" post, I can confirm that applying @sykesm's modification to my ~/.dvm/Vagrantfile worked like a charm on my Fusion 6/Vagrant 1.6.3 system.

from dvm.

This seems fixed with version 2.5.2 of the vagrant-vmware-fusion plugin. Works for me and also mitchellh/boot2docker-vagrant-box#48 (comment)

from dvm.