Updating Tools takes forever

[tolmasky]

box.update_guest_tools = true

Now takes forever. Seems like nothing is being downloaded.

[legal90]

Hi @tolmasky,
That would be great to get some more details to help you.

1. Do you use a public Vagrant box? If yes - please provide the name and version, so I'd be able to reproduce the issue.
2. What Parallels Desktop version are you using?
3. Please, attach the Parallels Tools installation log file (it is located in your VM): /var/log/parallels-tools-install.log. Or you can send it to me by e-mail.

[boucher]

Since upgrading to Parallels 12.1.1 I'm having the same problem. Here's the install log:

vagrant@ubuntu-16:~$ tail /var/log/parallels-tools-install.log 
Installation of Parallels Guest Tools version '12.1.0.41489' was found.
Created previous version backup in '/tmp/prltools-backup-RtKv6b.tar.gz'

Fri Dec  2 15:59:11 EET 2016
Start installation or upgrade of Guest Tools
new version of parallels tools
Found Guest Tools directory: /usr/lib/parallels-tools
Start removal of user space modules
Umounting Shared Folders: done
Shutting down Parallels tools daemon: done

We're both running the parallels/ubuntu-16.04 box, version 2.0.3.

[tolmasky]

For the record, Ubunto-14.04 on Parallels 12 seems to work, just not Ubuntuu-16.04

…

On Fri, Dec 2, 2016 at 6:03 AM, Ross Boucher ***@***.***> wrote: Since upgrading to Parallels 12.1.1 I'm having the same problem. Here's the install log: ***@***.***:~$ tail /var/log/parallels-tools-install.log Installation of Parallels Guest Tools version '12.1.0.41489' was found. Created previous version backup in '/tmp/prltools-backup-RtKv6b.tar.gz' Fri Dec 2 15:59:11 EET 2016 Start installation or upgrade of Guest Tools new version of parallels tools Found Guest Tools directory: /usr/lib/parallels-tools Start removal of user space modules Umounting Shared Folders: done Shutting down Parallels tools daemon: done We're both running the parallels/ubuntu-16.04 box, version 2.0.3. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#281 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABcyc2-mAJz2FlKR1SXzipfxtVD83sqks5rECUxgaJpZM4K-ZOL> .

-- Francisco Tolmasky www.tolmasky.com tolmasky@gmail.com

[killglance]

I am also hitting this problem on multiple boxes. For the sake of this issue, I've replicated @tolmasky problem using both 'parallels/centos-7.2' and 'parallels/ubuntu-16.04'. FWIW the behavior is also showing up with 'boxcutter/centos72' and 'boxcutter/centos68'

vagrant sits in it's ssh keepalive loop after issuing ptiagent-cmd --info

if i ssh into the box and run it myself, it dumps the following logs and possibly a helpful error message

Shutting down Parallels tools daemon: done 12-02 23:13:58.888 F /PTIAgentCmd:2555:2555/ Found self exec: /usr/lib/parallels-tools/installer/iagent64/ptiagent-cmd 12-02 23:13:58.890 F /PTIAgentCmd:2555:2555/ Found parent exec: /bin/bash 12-02 23:13:58.890 F /PTIAgentCmd:2555:2555/ Found grand parent exec: /bin/su 12-02 23:13:58.924 W PTIA_GUEST /PTIAgentCmd:2555:2555/ Tools state = 1 (oldNotation = 0) 12-02 23:13:58.925 W PTIA_GUEST /PTIAgentCmd:2555:2599/ Start installation (silent = 0 local = 0 onlyDownload = 0) 12-02 23:13:58.936 F PTIA_GUEST /PTIAgentCmd:2555:2599/ Unable to open file to store installation package. 12-02 23:13:58.960 F /PTIAgentCmd:2555:2599/ Command failed : umount "/root/". ExitCode=32 ErrorCode=5 12-02 23:13:58.960 W PTIA_GUEST /PTIAgentCmd:2555:2599/ Failed to unmount image with tools installer. 12-02 23:13:58.960 W PTIA_GUEST /PTIAgentCmd:2555:2599/ Installation result = 2

The above snippet is while using 'parallels/ubuntu-16.04'

if i reboot the box it comes up and passes version check just fine so the tools are successfully installing. Perhaps the agent failing to eject the media is whats hanging the vagrant plugin?

version info:
Parallels Pro -- Version 12.1.1 (41491)

Jon-Schulzs-MacBook-Pro:puppet jschulz$ vagrant --version
Vagrant 1.9.0
Jon-Schulzs-MacBook-Pro:puppet jschulz$ vagrant plugin list
vagrant-cachier (1.2.1)
  - Version Constraint: > 0
vagrant-hostmanager (1.8.5)
  - Version Constraint: > 0
vagrant-parallels (1.7.0)
  - Version Constraint: > 0
vagrant-serverspec (1.1.1)
  - Version Constraint: > 0
vagrant-share (1.1.6)
  - Version Constraint: > 0
vagrant-winrm (0.7.0)
  - Version Constraint: > 0

[legal90]

@tolmasky @boucher @killglance
Hi all,
Thank you for pointing on this issue and providing the details! In Parallels Desktop 12 there was implemented an auto-update of Parallels Tools in Linux guests, like the similar mechanism available in our Windows guests for years.
But unlikely the Vagrant-managed feature "update_guest_tools", this one is an internal stuff and initiated by Parallels Tools themselves.

The bad thing here is that such "built-in" auto-update happens in the background right after the VM boot. It works fine for regular VMs, but not for Vagrant (it even may break the provisioning: chef/bento#695 (comment)).
Our Vagrant provider knows nothing about that behavior and tries to upgrade Parallels Tools too (due to update_guest_tools option enabled in Vagrantfile). And seems like there is a collision of two ptiagent-cmd processes.

Hopefully, this internal auto-update could be disabled via prlctl CLI, so we can try this:

  config.vm.provider "parallels" do |prl|
    prl.customize ["set", :id, "--tools-autoupdate", "no"]
  end

I'd appreciate if you verify your cases with this block added in Vagrantfile. Does it help?

I'd like to disable it via default settings in our provider (link). So I hope this issue will be fixed in the next version of vagrant-parallels.

[killglance]

Ah, that explains why the logs looked like multiple instances of ptiagent-cmd were running concurrently.

my initial tests are looking promising i'll update the threat tomorrow morning once this server-spec run is finished. but I think this did the the trick for me

[killglance]

Yeah this worked for me across all my boxes @legal90 thanks so much for the workaround!

[ovr]

@legal90

I am having a similar problem with parallels/centos-7.2, latest from public
box.update_guest_tools = true infinity loading, looks like it's broken but it's not controlled by provider plugin that software exit
I am going to disable by box.update_guest_tools = false it's okey now

questions:

• will it be fixed in the near feature?
• when Parallels will update boxe(s) with latest Parallells guest additional?

Currently I am having

prlctl --version
prlctl version 12.1.1 (41491)

But box

12.1.0

Thanks

[legal90]

@killglance @ovr , thanks for the feedback!
The fix is on the way: #283, so the new provider version will be released very soon.
As well as newer boxes with latest Parallels Tools - I'll manage to build & publish them this week.

[legal90]

This issue should be fixed in v1.7.1

P.s. New boxes parallels/* with Parallels Tool 12.1.1 have been also published.