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

[Feature] Add remote target support for QEMU builder #10

Open
ghost opened this issue Apr 19, 2021 · 1 comment
Open

[Feature] Add remote target support for QEMU builder #10

ghost opened this issue Apr 19, 2021 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 19, 2021

This issue was originally opened by @stdevel as hashicorp/packer#7757. It was migrated here as a result of the Packer plugin split. The original body of the issue is below.


As far as I understood from the documentation, the QEMU builder does not support remote hosts running KVM/QEMU.
This means, you will need to run Packer on that host that also runs KVM.
It would be very useful to have the possibility to specify a hypervisor host and have Packer to connect to it via SSH (like the vsphere-iso builder).

@mdebord-dlr
Copy link

Adding here since this is a big priority in my use-case.

From what I can tell, currently the hypervisor must be used as the primary worker node for qemu with no way of orchestrating Packer from a CI/CD worker node or any other worker host. Everything must be done on the hypervisor locally which really is a hindrance to system/workflow design.

The community "libvirt" plugin does allow remote access (although it plays a different role versus qemu plugin, so it isn't a direct replacement). For example, it uses a "qemu://host.example.com/system" style connection string. Perhaps that same method of connecting could be adapted here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant