Re: [vagrant-up] Networking Problems with VMware Fusion + OSX 10.8 Host + OSX 10.8 Guest

[Anders Bruvik]

28. apr. 2013 kl. 23:04 skrev Jamie Alessio <ja...@stoic.net>:

> Now that we have VMware Fusion support for Vagrant, I'm interested in using Vagrant on OSX 10.8 to work on OSX 10.8 guest boxes.
>
> I used Veewee to successfully build an OSX 10.8 Vagrant box for the vmware_fusion provider, but I am unable to find any network configuration in my Vagrantfile that produces working networking in the guest OSX 10.8 operating system in VMware Fusion.
>
>

I am having the same problem. I have built the box manually using a 10.8 installer, the box is getting network if I boot it from vmware, but not if I boot it using vagrant.


--
Anders Bruvik

[Rodney Rosenda]

Hi,

I am assuming that you paid for the Fusion provider and are entitled to email support? What did you get as answer in case you submitted a support request?

Regards,

Rodney

On Sunday, April 28, 2013 11:04:05 PM UTC+2, Jamie Alessio wrote:

Now that we have VMware Fusion support for Vagrant, I'm interested in using Vagrant on OSX 10.8 to work on OSX 10.8 guest boxes.

I used Veewee to successfully build an OSX 10.8 Vagrant box for the vmware_fusion provider, but I am unable to find any network configuration in my Vagrantfile that produces working networking in the guest OSX 10.8 operating system in VMware Fusion. 

Here's the barebones Vagrantfile I'm using for now. I've tried using both the :public_network and :private_network configs with no notable success. I can get networking working in the guest OS by manually changing the network settings using the VMware Fusion GUI but not via Vagrant yet so I suspect there's a problem in how Vagrant is communicating with Fusion.

Vagrant.configure("2") do |config|

  config.vm.box = "osx_10.8.3_fusion"

  config.vm.box_url = "/Users/jamie/dev/chef/veewee/osx_10.8.3_fusion.box"

end

Running vagrant up...

>> vagrant up --provider vmware_fusion

Bringing machine 'default' up with 'vmware_fusion' provider...

[default] Cloning VMware VM: 'osx_10.8.3_fusion'. This can take some time...

[default] Verifying vmnet devices are healthy...

[default] Preparing network adapters...

[default] Starting the VMware VM...

[default] Waiting for the VM to finish booting...

It hangs at this point forever because it cannot communicate with the guest machine. Using the VMware Fusion GUI to login to the guest OS confirms that there is no networking available in the guest OS.

On the OSX 10.8 guest:

vagrant-osx-108:~ vagrant$ ifconfig

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384

  options=3<RXCSUM,TXCSUM>

  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 

  inet 127.0.0.1 netmask 0xff000000 

  inet6 ::1 prefixlen 128 

gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280

stf0: flags=0<> mtu 1280

I have tried all the things in this post by Mitchell and the contents of my /Library/Preferences/VMware\ Fusion/networking is available in this gist.

Additionally, I have discussed this on IRC with tvsutton (author of the Veewee tools I used to create the box) and he is experiencing the same issue (inability to get networking in a OSX 10.8 guest with Fusion), so this is at least repeatable on at least one other box.

I'm brand new to VMware Fusion so if anyone has ideas on things to try next I'd be grateful. Thanks!

- Jamie

[Timothy Sutton]

No luck yet, your findings echo mine.

When I have some more time I'd like to try to step through the Vagrant code to get a box configured and inspect the system before it boots, to try to compare it with that of a working, manually-configured Fusion VM. Someone more familiar with the codebase could probably do this in short order. I'm not familiar with any of the advanced Fusion config going on that the provider is leveraging, either, so this would also be something I'd probably have to poke at for quite a while.


-Tim

On 2013-05-09, at 6:50 AM, Zsolt Dollenstein <zsol...@gmail.com> wrote:

> Hi Tim,
>
> any luck with your issue? I just hit this exact same problem.
> One additional thing I noticed is when I go into System Settings on the guest machine, I see a single "Ethernet" interface which is in a "disconnected" state, but according to the vmware gui, there should be two network interfaces, both of them connected. I can see some vmnet-{dhcpd,bridge,netifup} processes running on the host machine corresponding to these interfaces.
>
> On Thursday, May 2, 2013 3:49:49 PM UTC+2, Timothy Sutton wrote:
> I did and am, and did ping Mitchell on the issue a week after the provider was released, on IRC and via e-mail support, with steps to reproduce and a sample box.
>
> He acknowledged the issue but as I'm sure he's very busy, has not followed up further.
>
>
> -Tim

> --
> You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/VyZBqzbVzvs/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Timothy Sutton]

At least one person has confirmed this with a manually-built box. It was either in a thread on this list or on Twitter, can't remember.

Tim

On 2013-06-07, at 12:16 PM, Kristian Botnen <kristia...@gmail.com> wrote:

Hi,

Can confirm this issue too.

But I have one question, is everybody using veewee to create the box that does not work? Anyone manually created the box confirming this issue?

-Kristian

[Dave Casey]

I am new to Veewee (and to Vagrant, for that matter) and will need to set up some OSX 10.8 guests soon. Could you outline the steps you took to set up your box so I can try to reproduce the issue you are seeing?

Thanks,

-Dave

[Anders Bruvik]

7. juni 2013 kl. 19:26 skrev Timothy Sutton <t...@synthist.net>:

> At least one person has confirmed this with a manually-built box. It was either in a thread on this list or on Twitter, can't remember.
>

It was me who confirmed it on twitter.

--
Anders

[Mrinal Wadhwa]

Hey Everyone,

I'm facing the same issue, did anyone here find a solution?

Attached is a debug log.

Thank you,

Mrinal

[Mitchell Hashimoto]

Hi all,

Sorry for not responding sooner to this. There are a group of people out there successfully running OS X guests with Vagrant. Unfortunately, no one has really documented how to do this yet (and I haven't tried yet). There was a bug in the Fusion plugin fixed two weeks ago where it was actually stripping important networking information from the OS X VM. With that fix, the person I was doing support for was able to get things working.

However, the issue remains that there are parts of Vagrant that aren't OS X guest compatible, mainly because Vagrant is missing an OS X guest implementation: http://docs.vagrantup.com/v2/plugins/guests.html

I plan on improving OS support across the board in future versions of Vagrant, it is one of the big three features towards 2.0 that I have always had planned since I started work on 1.1 over a year ago.

In the mean time, some hacks are required, but technically there is nothing stopping from Vagrant successfully starting/stopping an OS X VM. You'll probably run into problems getting hostonly, etc. networks working, though.

Best,

Mitchell

[Timothy Sutton]

Thanks for the update Mitchell. I just updated to 0.6.5 of the provider, but still had the same results. I decided to dig a bit more again, since it's been a while since I looked, and the provider has seen many revisions.

Going through the debug output, nothing really jumped out at me, given that the hardware doesn't even appear in the guest VM. I don't know how I missed this earlier when I was comparing .vmx files, but now I see it. This entry is evidently crucial for an OS X guest, and isn't explicitly set by the provider before the VM boots:

ethernet0.virtualDev = "e1000"

If I add the line and boot the VM manually with the Fusion GUI, I have a working ethernet device with NAT.

And thankfully, I can just set this custom .vmx config in my Vagrantfile, ie.:

  config.vm.provider :vmware_fusion do |v|

    v.vmx['ethernet0.virtualDev'] = 'e1000'

  end

I'm curious now what the default virtual ethernet device is for Fusion (Realtek?), since the E1000 is evidently what Patrick chose for his VMX template when he wrote the Fusion provider for VeeWee.

Now Vagrant reaches the machine, and of course complains it doesn't know how to configure it. Looks like I can finally start to muck around with the guest plugin!

-Tim

[Zsolt Dollenstein]

I'll give this workaround a go later today. Thanks Tim!

--

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/VyZBqzbVzvs/unsubscribe.

[Zsolt Dollenstein]

I can confirm this workaround works :)