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

"use_linked_clone" fails in parallel mode #206

Closed
legal90 opened this issue Aug 26, 2015 · 5 comments
Closed

"use_linked_clone" fails in parallel mode #206

legal90 opened this issue Aug 26, 2015 · 5 comments
Assignees

Comments

@legal90
Copy link
Collaborator

legal90 commented Aug 26, 2015

If you run vagrant up for the first time in multi-machine configuration, it fails with error telling that prlctl clone --linked couldn't be executed concurrently. It mostly like a Parallels Desktop issue, but should be worked around on the "vagrant-parallels" side.

Vagrantfile:

Vagrant.configure(2) do |config|
  config.vm.box = "parallels/centos-6.6"

  config.vm.define "centos_1"
  config.vm.define "centos_2"
  config.vm.define "centos_3"

  config.vm.provider "parallels" do |prl|
    prl.use_linked_clone = true
  end
end
$ vagrant up

<...>

An error occurred while executing the action on the 'centos_3'
machine. Please handle this error then try again:

There was an error while command execution. The command and stderr is shown below.

Command: ["/usr/local/bin/prlctl", "clone", "centos-6.6-x86_64", "--name", "centos-6.6-x86_64_1440573847293_55601", "--linked", "--id", "66adbac3-9fa7-410f-bbad-3ac58fa6f8f1"]

Stderr:
Failed to clone the VM: The virtual machine could not be found. The virtual machine is not registered in the virtual machine directory on your Mac. Contact the Parallels support team for assistance.

Parallels Desktop 11.0.0 (31193)
vagrant-parallels v1.4.2

@legal90 legal90 self-assigned this Aug 26, 2015
@legal90
Copy link
Collaborator Author

legal90 commented Aug 26, 2015

Fixed in v1.4.3

@tradel
Copy link

tradel commented Jul 11, 2018

Still an issue in 1.7.8.

First machine errored with:

Command: ["/usr/local/bin/prlctl", "unregister", "0b2fbbe0-8bd7-452d-94e6-f2f2c2b9941d"]

Stderr: Failed to unregister the VM: Unable to perform the action because the virtual machine is busy. The virtual machine is being cloned. Please try again later.

Second machine errored with:

padding error, need 74192792 block 16

@max-arnold
Copy link

I also often get hit by this:

Command: ["/usr/local/bin/prlctl", "unregister", "e75da2c8-df22-4562-ba86-8ba81c3dbbe9"]

Stderr: Failed to unregister the VM: Unable to perform the action because the virtual machine is busy. The virtual machine is being cloned. Please try again later.
% vagrant version
Installed Version: 2.2.9
Latest Version: 2.2.9

% vagrant plugin list
vagrant-parallels (2.0.1, global)

Parallels 15.1.4 (47270)

@cecilphillip
Copy link

I'm get this error too. Using the same versions as @max-arnold
cc @legal90

@max-arnold
Copy link

@tradel @cecilphillip I just upgraded to 2.1.0 and it looks like the issue was fixed in #370

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

No branches or pull requests

4 participants