Cannot start boxes with vmware_desktop provider with VMware WS Pro 17 on Linux

[Salvor42]

I have a licensed provider installed:

$ vagrant plugin list
vagrant-vmware-desktop (3.0.3, global)

$ dpkg -l | grep vagrant-vmware
ii  vagrant-vmware-utility                        1:1.0.22                           amd64        Vagrant utility for VMware Workstation and Player

But I cannot start any box:

$ vagrant up 
Bringing machine 'default' up with 'vmware_desktop' provider...
==> default: Box 'hashicorp/bionic64' could not be found. Attempting to find and install...
    default: Box Provider: vmware_desktop, vmware_fusion, vmware_workstation
    default: Box Version: >= 0
==> default: Loading metadata for box 'hashicorp/bionic64'
    default: URL: https://vagrantcloud.com/hashicorp/bionic64
==> default: Adding box 'hashicorp/bionic64' (v1.0.282) for provider: vmware_desktop
    default: Downloading: https://vagrantcloud.com/hashicorp/boxes/bionic64/versions/1.0.282/providers/vmware_desktop.box
==> default: Successfully added box 'hashicorp/bionic64' (v1.0.282) for 'vmware_desktop'!
==> default: Cloning VMware VM: 'hashicorp/bionic64'. This can take some time...
An error occurred while executing `vmrun`, a utility for controlling
VMware machines. The command and output are below:

Command: ["-T", "player", "snapshot", "/home/miesen/.vagrant.d/boxes/hashicorp-VAGRANTSLASH-bionic64/1.0.282/vmware_desktop/ubuntu-18.04-amd64.vmx", "3dd9736f-aa7a-4564-a9c2-e45c3e92fff7", {:notify=>[:stdout, :stderr]}]

Stdout: Error: The operation is not supported

Stderr: 

Of course, the player does not support snapshots (AFAIK). I tried vmrum -T ws ... by hand, which worked. What can I do to prevent the player to be chosen?

Reproduction information

Vagrant version

Vagrant 2.3.7

Host operating system

Debian GNU/Linux 11 (bullseye)

Vagrantfile

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

  config.vm.box = "hashicorp/bionic64"

  config.vm.box_check_update = false

end

[chrisroberts]

Hi there,

Would you please provide a gist of the output from vagrant up --debug.

Thanks!

[Salvor42]

Of course:

https://gist.github.com/Salvor42/1837b06992a560d2375c0bf4d6ef1bd0

Thank you for your effort!

[eddiezab]

I just ran up into this. The solution (or I'd rather way a workaround) that worked for me is here.

My service file was is a different location, but the key part is the -license-override professional

[jovmarkovic]

-license-override professional Worked for me as well.

[ssplatt]

I'm trying to use this in Github Actions with Packer and a "standard" / "personal" license. Using the suggestions to force a license type does not fix the issue, it hangs at "Calling Vagrant Up (this can take some time)...". Dropping to version 3.0.1 has the same effect. I'm using ...vmw-desktop/ws/17.5.2/23775571/linux/core/VMware-Workstation-17.5.2-23775571.x86_64.bundle.tar as the vmware version.

[ssplatt]

Does it sound like the root cause may be similar to https://github.com/hashicorp/packer-plugin-vmware/issues/229 ?

[chrisroberts]

@ssplatt is the host you are running on for github actions bare metal or does it support nested virtualization?

[chrisroberts]

And sorry for the late reply here. The output of:

/usr/lib/vmware/bin/vmware-vmx --query-license LicenseEdition

would be helpful in determining if the matching needs to be modified. Thanks!

[Salvor42]

Short comment: I'm no longer on topic, since I went to Proxmox in my homelab. But I'm happy if this thread leads to something useful! Thank you for your time!