Parallels Tools vagrant installation success then failure with Ubuntu 12.04

Discussion in 'Linux Virtual Machine' started by RobbS, Nov 11, 2015.

  1. RobbS

    RobbS Bit poster

    Messages:
    1
    The Tools seem to install just fine and the VM runs, after the very first `vagrant up` only. However, on every successive `vagrant up` with that already setup vm, problems with Parallels Tools prevents sharing directories.

    Has anyone else run into this?

    Very odd errors every time I try `vagrant up`:

    ==> default: Checking for Parallels Tools installed on the VM...

    ==> default: Parallels Tools were not detected on this VM! They are required

    ==> default: for forwarded ports, shared folders, host only networking and more.

    ==> default: If SSH fails or shared folders are not working on this machine,

    ==> default: please install Parallels Tools within the virtual machine and

    ==> default: reload your VM.

    ==> default: Installing the proper version of Parallels Tools. This may take a few minutes...

    ==> default: Parallels Tools have been installed. Rebooting the VM...

    ==> default: Attempting graceful shutdown of VM...

    ==> default: Running 'pre-boot' VM customizations...

    ==> default: Booting VM...

    ==> default: Waiting for machine to boot. This may take a few minutes...

    default: SSH address: 10.211.55.19:22

    default: SSH username: vagrant

    default: SSH auth method: private key

    default: Warning: Connection timeout. Retrying...

    default: Warning: Connection timeout. Retrying...

    default: Warning: Host appears down. Retrying...

    ==> default: Machine booted and ready!

    ==> default: Configuring and enabling network interfaces...

    ==> default: Mounting shared folders...

    default: /vagrant => /Users/robb/src/weblaws

    Failed to mount folders in Linux guest. This is usually because

    the "prl_fs" file system is not available. Please verify that

    Parallels Tools are properly installed in the guest and

    can work properly. If so, the VM reboot can solve a problem.

    The command attempted was:


    mount -t prl_fs -o uid=`id -u vagrant`,gid=`getent group vagrant | cut -d: -f3` vagrant /vagrant

    mount -t prl_fs -o uid=`id -u vagrant`,gid=`id -g vagrant` vagrant /vagrant
     
  2. oztrev

    oztrev Member

    Messages:
    99
    Vagrant support was moved to the Pro version of PD11. You don't mention which version you're using...
     
  3. Maria3

    Maria3 Bit poster

    Messages:
    1
    Hi, I'm having same issues. I'm using Parallels Desktop 10.3.0.
     

Share This Page