-
Notifications
You must be signed in to change notification settings - Fork 139
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
Parallels Box Error #3
Comments
Getting the same error. |
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.
|
For now I switched to VirtualBox, but I'll take a look later into the Parallels command set. |
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.
|
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:
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. |
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 |
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.
|
I tried to run this box seems to be getting the error
The text was updated successfully, but these errors were encountered: