Parallels Box Error about robox

[Tatsh]

Getting the same error.

[ladar]

My guess is there is a problem with the syntax in the bundled Vagrantfile. I'm traveling at the moment, so I can't test variations, and  I don't use Parallels much to begin with. Perhaps you can suggest the fix? As you can see, there are 4 arguments given to the customize function. What is the correct syntax? Should it only be the last two? ```   config.vm.provider :parallels do |v, override|     v.customize["set", :id, "--on-window-close", "keep-running"]     v.customize["set", :id, "--startup-view", "headless"]     v.customize["set", :id, "--memsize", "2048"]     v.customize["set", :id, "--cpus", "2"]   end ``` Sadly I haven't done much testing with the Hyper-V/Parallels boxes, as the notebook computers I use to build those images are painfully slow. So improvements are welcome.

…

On 08/19/2018 02:20 PM, Andrew Udvare wrote: Getting the same error.

[Tatsh]

For now I switched to VirtualBox, but I'll take a look later into the Parallels command set.

[ladar]

I was able to confirm the syntax I used to set the options was wrong. I'm trying to perform a full rebuild of all boxes this week, but I'll hold off on the Parallels build for the moment, until I get we can figure out what the correct syntax is. Anybody know? Pull request welcome.

…

On 08/20/2018 11:20 AM, Andrew Udvare wrote: For now I switched to VirtualBox, but I'll take a look later into the Parallels command set.

[ladar]

I'm still investigating, but I tracked down the documentation. My config appears to match the docs available at:

http://parallels.github.io/vagrant-parallels/docs/configuration.html#prlctl

Which explicitly states:

Multiple customize directives can be used simultaneously. They will be executed in the given order.

I'll have to check, but perhaps that doesn't mean what it says. Multiple options can be specified, but they all must appear as part of a single customize directive.

[ladar]

Adding a space between customize, and the opening "[" appears to fix the issue. If you don't want to wait for the next build, feel free to edit the ~/.vagrant.d/boxes/generic-VAGRANTSLASH-BOXNAME/1.8.14/parallels/Vagrantfile file directly. Just replace BOXNAME with the distro in question. Please reopen if the issue resurfaces.

[ladar]

The v1.2.24 build ran into issues with some of the other hypervisors, so you can expect a v1.2.26 build relatively soon. That said, the Parallels robot was the only one that managed to finish building all of its generic boxes. I tested the centos7 image and it's working fine. Sadly, my Parallels robot is an 8 year old Macbook Air, and to slow for me to check the resulting box images automatically, like I do with the VMWare, Virtualbox and libvirt images. (The Hyper-V robot is also a senior citizen). Long story short, if you run into more problems with the Parallels images, please let me know, and I'll take look, as I can't effectively test them all myself, with any frequency right now.

bash-3.2$ vagrant plugin install vagrant-parallels
Installing the 'vagrant-parallels' plugin. This can take a few minutes...
Fetching: mini_portile2-2.3.0.gem (100%)
Fetching: nokogiri-1.8.4.gem (100%)
Building native extensions.  This could take a while...
Fetching: vagrant-parallels-1.7.8.gem (100%)
Installed the plugin 'vagrant-parallels (1.7.8)'!
bash-3.2$ vagrant up --provider parallels
Bringing machine 'default' up with 'parallels' provider...
==> default: Box 'generic/centos7' could not be found. Attempting to find and install...
    default: Box Provider: parallels
    default: Box Version: >= 0
==> default: Loading metadata for box 'generic/centos7'
    default: URL: https://vagrantcloud.com/generic/centos7
==> default: Adding box 'generic/centos7' (v1.8.24) for provider: parallels
    default: Downloading: https://vagrantcloud.com/generic/boxes/centos7/versions/1.8.24/providers/parallels.box
==> default: Successfully added box 'generic/centos7' (v1.8.24) for 'parallels'!
==> default: Registering VM image from the base box 'generic/centos7'...
==> default: Cloning new virtual machine...
==> default: Unregistering the box VM image...
==> default: Setting the default configuration for VM...
==> default: Checking if box 'generic/centos7' is up to date...
==> default: Setting the name of the VM: centos7_default_1534990472080_67322
==> default: Preparing network interfaces based on configuration...
    default: Adapter 0: shared
==> default: Clearing any previously set network interfaces...
==> 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.3:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Checking for Parallels Tools installed on the VM...
==> default: Parallels Tools were not detected on this VM! They are required
==> default: for shared folders, time sync and more. If shared folders are not
==> default: working on this machine, please install Parallels Tools within the
==> default: virtual machine and reload your VM.