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

Configuration for PVM does not work when using packer on an M1 #49

Open
chargio opened this issue Aug 20, 2022 · 0 comments
Open

Configuration for PVM does not work when using packer on an M1 #49

chargio opened this issue Aug 20, 2022 · 0 comments
Labels

Comments

@chargio
Copy link

chargio commented Aug 20, 2022

Overview of the Issue

A packer build with an existing PVM does not find the file if it is in a different folder and you use spaces or ~ (even though it is explictly stated it will work)

Reproduction Steps

Create a packer file that points to a PVM, parallels-pvm type
packer build or packer validate
it won't be able to find the file

Steps to reproduce this issue

Plugin and Packer version

Packer v1.8.3
prlctl version 18.0.0 (53049)
packer-plugin-parallels_v1.0.3_x5.0_darwin_arm64

Simplified Packer Buildfile

packer {
required_plugins {
parallels = {
version = ">= 1.0.0"
source = "github.com/hashicorp/parallels"
}
}
}

source "parallels-pvm" "base-fedora" {
source_path = "/Users/sergio/Parallels/Fedora_36_tools.pvm"
parallels_tools_flavor = "lin-arm"
ssh_private_key_file = "./keys/vagrant"
ssh_username = "vagrant"
ssh_password = "vagrant"
ssh_timeout = "90s"
shutdown_command = "echo 'vagrant' | sudo -S shutdown -P now"
boot_wait = "5s"
}

build {
sources = ["source.parallels-pvm.base-fedora"]
}

Operating system and Environment details

Mac OS Monterey on an M1 Max

Log Fragments and crash.log files

Include appropriate log fragments. If the log is longer than a few dozen lines,
please include the URL to the gist of the log or
use the Github detailed format instead of posting it directly in the issue.

Set the env var PACKER_LOG=1 for maximum log detail.

@chargio chargio added the bug label Aug 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant