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

M1 macs: registering macOS VM images #420

Closed
strega-nil opened this issue Apr 14, 2022 · 1 comment
Closed

M1 macs: registering macOS VM images #420

strega-nil opened this issue Apr 14, 2022 · 1 comment

Comments

@strega-nil
Copy link

Hi all!

We're using vagrant-parallels to run our CI VMs, and it seems like there is an issue with spinning up macOS VMs on our M1s.

We set up the box using the standard method - downloading the parallels VM, and then making modifications to it, then tar'ing it up. When we try to run it, we get the following output:

vcpkg@CPPMAC-ARM64-01 build-box % vagrant up
Bringing machine 'default' up with 'parallels' provider...
==> default: Registering VM image from the base box 'vcpkg/macos-base'...
Parallels VM image (*.pvm) could not be found in the directory of
'vcpkg/macos-base' box. This is usually because the image has been removed manually.
Please remove the box, re-add it, and try again.

when I tried to fix that by also searching for .macvm files, (since that seems to be the new extension), I get this error:

vcpkg@CPPMAC-ARM64-01 build-box % vagrant up
Bringing machine 'default' up with 'parallels' provider...
==> default: Registering VM image from the base box 'vcpkg/macos-base'...
There was an error while command execution. The command and stderr is shown below.

Command: ["/usr/local/bin/prlctl", "register", "/Users/vcpkg/.vagrant.d/boxes/vcpkg-VAGRANTSLASH-macos-base/0/parallels/macOS 12.macvm", "--preserve-uuid"]

Stderr: Failed to register the VM: The configuration file you specified is invalid. Make sure that the specified file is a valid Parallels virtual machine configuration file and it is not corrupt, or select another file.

I'm well aware this might just be an issue on our end, so sorry if I screwed up creating the box...

@legal90
Copy link
Collaborator

legal90 commented Dec 19, 2022

Hi @strega-nil ,
It should be now fixed in v2.2.6 (by #429)

@legal90 legal90 closed this as completed Dec 19, 2022
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

2 participants