Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Salvor42 opened this issue Sep 8, 2023 · 10 comments
Assignees

Comments

@Salvor42
Copy link

Salvor42 commented Sep 8, 2023

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 chrisroberts transferred this issue from hashicorp/vagrant Sep 8, 2023
@chrisroberts chrisroberts self-assigned this Sep 8, 2023
@chrisroberts
Copy link
Member

Hi there,

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

Thanks!

@Salvor42
Copy link
Author

Salvor42 commented Sep 9, 2023

Of course:

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

Thank you for your effort!

@eddiezab
Copy link

eddiezab commented Oct 9, 2023

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
Copy link

-license-override professional Worked for me as well.

@ssplatt
Copy link

ssplatt commented Jul 15, 2024

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
Copy link

ssplatt commented Jul 24, 2024

Does it sound like the root cause may be similar to hashicorp/packer-plugin-vmware#229 ?

@chrisroberts
Copy link
Member

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

@chrisroberts
Copy link
Member

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
Copy link
Author

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!

@ssplatt
Copy link

ssplatt commented Oct 18, 2024

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

yes, they do. I believe the problem I'm running into now is that the free license cannot be set without VMware trying to pop up a gui at first run. I have a line to touch a license file but that isn't getting rid of the first run workflow.

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!

I ran this on my local host and got no output. I'm trying to use the free, personal license.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants