Open mikoday opened 1 month ago
Hi @mikoday,
By default the display
option is set to GTK for the plugin, so if you're trying to run a build on a Windows machine, chances are it'll fail.
You can change that by setting the display
option to none
, which will default to what the local binary supports.
We can probably change the default value to be none
for future releases, but I'm concerned this is a potential breaking change for existing templates, so this will likely not happen soon.
In the meantime I suggest changing this to none
, or one of the other supported values, which you can get from the help for qemu: qemu --help | grep display
should list the possibilities for your implementation.
Also if you don't need to run the build with a visual window for qemu, you can run headless (with headless = true
in the configs) and use VNC to connect to the machine independently, the logs give you a URI/port for that purpose.
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
Overview of the Issue
I'm trying to prepare a Windows image to use on maas, I also described my issue here: https://github.com/canonical/packer-maas/issues/272
Reproduction Steps
/home/maas/packer-maas/windows# make windows ISO=/home/maas/en-us_windows_11_business_editions_version_24h2_x64.iso VERSION=11 windows.json PACKER_LOG=1
Plugin and Packer version
v1.1.0
Simplified Packer Buildfile
If the file 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.
Operating system and Environment details
OS, Architecture, and any other information you can provide about the environment.
Log Fragments and crash.log files
Set the env var
PACKER_LOG=1
for maximum log detail.