Vagrant vmware provider fails to work with Fusion Tech Preview #22
Comments
|
I am suspecting this basically comes down to dealing with running an unsupported architecture (running x86-64 on ARM64), as mentioned in VMWare knowledge article 84273.
There are three issues here from a user perspective that needs to be fixed:
AFAIK, it seems the most likely route is to download the ARM image for Ubuntu and create a box based on that.
|
|
I was looking into this a few weeks ago (2021-09-23 according to my notes) and reached the same error message as you. Digging through the provider code, I think it was erroring on trying to parse the version output from the And then at it defines a regex to extract the version that doesn't match the above.vagrant-vmware-desktop/go_src/vagrant-vmware-utility/driver/base_posix.go Lines 109 to 113 in 7b26510 I've failed to document how I found this, but I think I was running which in turn loops me back round to the provider code I've noted above parsing the version number out of the vmx binary output. |
|
Ah, I see #16 fixed the version parsing mismatch and utility v1.0.21 has been released with the fix in it. |
|
Hmm ... good insights! I am really wondering how I ended up with 1.0.20 release, when the 1.0.21 fix arrived one week prior to me filing a bug. Pretty sure I was installing all of this just a day or two prior to filing the bug. But I will recheck! Did you get it working for you, using the 1.0.21 release, btw? Just as an additional thing: I did end up creating an ARM image in the end and test that out as well, but I did not get any further. Just crashed with the very general error message. The Ubuntu Impish Indri image is now available on Vagrant Cloud, if anyone else would like to have a go. I will retry with the 1.0.21 fix when time permits, to see if this all just comes down to parsing the version number. |
|
Nope. |
|
Got a different error message with VMware Fusion (release 18656771) Same version as you |
|
With the following installed versions of vagrant utility, vagrant plugin and vmware fusion itself: and a Vagrantfile set to use @fatso83's box (thanks!) Vagrant.configure("2") do |config|
config.vm.box = "fatso83/impish64-arm"
config.vm.provider "vmware_desktop" do |v|
v.gui = true
v.memory = "1024"
end
endRunning I can reproduce it running the Looking at the docs, I can see https://www.vagrantup.com/docs/providers/vmware/configuration#linked-clones states you can do a full clone instead of a linked clone. Updating the Vagrantfile with this then leads my VM to booting at least. Vagrant gets stuck at "Waiting for the VM to receive an address" stage, although I can see the VM has booted with the GUI enabled. Vagrant.configure("2") do |config|
config.vm.box = "fatso83/impish64-arm"
config.vm.provider "vmware_desktop" do |v|
v.gui = true
v.memory = "1024"
v.linked_clone = false
end
end |
|
@caius I managed to get the same error as you by making a symlink |
|
@yyounes75 oh interesting, mine's already at |
|
@caius This is very promising! At least that's the farthest I have seen anyone come to something working, at least 😄 Btw, this "Error: The file is already in use" thing, is this somehow caused by me not creating the box properly or is it something else? It's my second attempt at creating a box (all related to this issue), but I just followed a general guide, but I might have missed something. I think I removed all lock files I could find, at least. With regards to this:
There is no gui. I just created a plain server image with no gui packages installed. I don't know what the
I think that's pretty certain. The Tech Preview will install alongside any other "stable" release. Maybe the provider should be able to pick up some override from an environment variable or something else to try and find the VMWare install in an alternative location? |
|
|
|
So it basically seems you have been able to get everything working, apart from networking (which fails due to something out of our control)? |
|
Thanks to @caius the VM from @fatso83 can start but vagrant hangs at startup, it seems it can't fetch the ip address. Some debug logs : EDIT: |
|
This is a longshot, but maybe other paths differ in the tech preview as well? This is from Might be worth checking if the paths in |
|
All paths are good on my side unless the |
|
Hi there, The network detection bits are working as expected. I pulled down the box and after inspect it the reason the networking is failing is due to the predictable network interface names being used. I built out a quick box to verify things (which is why it's large, I didn't take the time to prune anything out) but you can test it out and see how it's working for you locally: https://app.vagrantup.com/spox/boxes/ubuntu-arm/versions/1.0.0 |
|
@chrisroberts Just started on this today and got it to work with the box you posted. Thank you! I did not do much yet but Big thank you as well to all previous contributors to this issue @fatso83 @caius @yyounes75 who saved me a huge amount of time. |
|
@chrisroberts I am not that well versed in the Vagrantverse, so I was unsure of what this referenced:
Some searching led me to this gist talking about just this:
This is what you are talking about, right? If so, I should be able to do the changes mentioned there and upload a new patched version of my existing image. Edit: another relevant reference: hashicorp/vagrant#9222 |
|
Seems like the bento templates take this into account: https://github.com/chef/bento/pull/1014/files I will try and fix the current image. If time permits (not likely), it would be nice to supply a new PR for the bento project so that they have an ARM template as well. @sbailliez and @chrisroberts Any chance of you writing up the steps required to get to a working system? The thread is getting a tad bit long. It does not seems like we need to customize the spox box by setting |
|
@fatso83 here are part of the notes I wrote down this weekend with all the steps: https://gist.github.com/sbailliez/f22db6434ac84eccb6d3c8833c85ad92 - Let me know if something is confusing, missing or incorrect. |
|
As already mentioned above the network problems are really related to the predictable network interface names. I've uploaded two boxes for the VMware provider: Ubuntu Server 20.04 I tested several vagrant configurations and everything seems to work. |
|
Hello. Any new updates on this ? I am still having issues. Thank you. Using box: https://app.vagrantup.com/rkrause/boxes/ubuntu-20.04-arm64 ➜ Vagrant /opt/vagrant-vmware-desktop/bin/vagrant-vmware-utility -v ➜ Vagrant vagrant plugin list |
|
@neuraload Kind of hard to help you when you don't supply a reproducible test case. You could be missing any number of steps. Have you followed @sbailliez gist instructions to the letter? |
|
@fatso83 Sorry for not providing additional information. Yes, I followed @sbailliez gist instructions and it doesn't work. If there is any info I can provide please let me know. Thank you. @fatso83 Hello. It seems that reinstalling the vagrant-vmware-utility made this work, I just wanted to see if it would help and it did. Wierd I must say. |
|
@neuraload I guess creating a StackOverflow question (and posting the link here) where you detail all the steps involved, including verifying what works at which stage, would give you the best chances of getting some help finding out. As you can see from this thread, there are many steps along the way where we get valuable diagnostic output. To me, it is unclear at which step you get problems and which of the steps were successful and not. I don't think I can help, as I don't use Vagrant (apart from this experiment, which was valuable in itself), but others (especially on SO) will have different incentives. I will close this issue, as the provider does work with VMWare Fusion Tech Preview on ARM, but it does not work all that great from a user perspective. I think some issues/feature requests that should exist would be:
|
|
Hi, Getting the following error. I wonder if anyone of you could assist me to install vagrant in my M1 machine. Thanks in advance |
There is way too little reproduction info here to help you out. You don't even list what you have tried, like the commands and what you have tried after googling a bit. AFAIK, Vagrant recommends you download their binaries anyhow, so try that first. And GitHub really is not the place for issues like this. Try SuperUser or some some Homebrew forum. |
Hi, I am running an Apple Silicon Macbook (ARM) and found out that VirtualBox does not work on that platform. I then learned that VMWare released a Tech Preview of Fusion for ARM last month, and so I was hopeful in getting that to work with Vagrant, as you provide a VMWare provider.
I followed all the steps for installing the provider and you can see from the output that it seems to work. I then proceeded to follow the Getting Started guide (skipping the install of VirtualBox). You could also see my own notes when doing this. All seemed fine up until the last steps:
When running with the debug output, it seems as if it could not find any image matching the supplied image. I am not that familiar with Vagrant, but I assumed it might have to do with the image needing to specifically work with VMWare? So I searched vagrant images for anything support vmware and tried both
"generic/ubuntu2104"and"roboxes/ubuntu2104"which both were tagged vmware. No luck there either; they all erred with something like this in the debug outputThe following is info following the Bug template
Debug output
https://gist.github.com/fatso83/7da6c48debb4b48333feab90b44964d8
Expected behavior
That it fired up a vm as described in getting started
Actual behavior
It erred with
Steps to reproduce
The text was updated successfully, but these errors were encountered: