# Create Windows image with "libvirt" builder

**URL:** <https://discuss.hashicorp.com/t/create-windows-image-with-libvirt-builder/53371>\
**Category:** Packer\
**Created:** [May 3, 2023, 9:55am UTC](https://discuss.hashicorp.com/t/create-windows-image-with-libvirt-builder/53371 "2023-05-03T09:55:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlexisVarela](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/alexisvarela/32/33593_2.png) [@AlexisVarela](https://discuss.hashicorp.com/u/AlexisVarela)\
**Post date:** [May 3, 2023, 9:55am UTC](https://discuss.hashicorp.com/t/create-windows-image-with-libvirt-builder/53371/1 "2023-05-03T09:55:22Z")

</div>

Have you ever tried to create Windows images with the “Libvirt” builder?

I want to use this builder instead of “qemu” because I would like to do CI/CD. That is, to have a Packer runner in GitLab starting the image creation processes on a remote hypervisor from where “Libvirt”, it’s possible to specify to Packer a URL. My problem is mainly with the average documentation and the complexity of the volume configurations.

If anyone knows and can enlighten me I am a taker.
