packer crash while running post-processor (type vagrant)
- Dominant language
- Go
- Stars
- 15.8k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
#### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
#### Overview of the Issue
Packer crash while building vagrant image.
Running packer inside a VMware virtual machine (Debian 11), bare-metal host is Windows 11. Nested virtualization is enabled. Using a slightly modified version of https://github.com/rgl/windows-vagrant to install win11-uefi, with virtualbox as the vagrant virtualization provider.
#### Reproduction Steps
Have only seen the issue once, but...the crash log states "This is always indicative of a bug within Packer" so....
### Packer version
Packer v1.8.7
### Simplified Packer Template
git clone https://github.com/rgl/windows-vagrant
cd windows-vagrant
make build-windows-11-22h2-uefi-virtualbox
I've modified the windows-11-22h2-uefi/autounattend.xml file from rgl's upstream version, but the crash appears to during some built-in packer steps (e.g. after my target vm has already been exported to ovf and the vm deleted from virtualbox), so I'm don't think that matters.
### Operating system and Environment details
* Bare metal host: Windows 11
* Running packer inside VMware virtual machine, Debian 11
** nested virtualization enabled, running virtualbox "inside" the debian VM works as expected
* Vagrant 2.3.4
* VirtualBox 7.0.8r156879
### Log Fragments and crash.log files
[crash.log](https://github.com/hashicorp/packer/files/11512753/crash.log)
Contributor guide
Assessment
This issue has not been assessed yet.