floppy image not detected by Windows installer when booting in uefi firmware mode

[FrankAtHome]

When Autounattend is provided as a floppy image, the Windows installer (unmodified Windows 2022 eval ISO) picks it up successfully when booting in legacy bios mode.

As soon as firmware mode is switched to uefi, the Windows installer no longer picks up the Autounattend.xml file when served through a floppy image.

As a workaround, I've incorporated Autounattend.xml in the root of the guest tool iso file specified with tools_iso_name

[M1gh7yP1r473]

Will try that also...problem is current XenServer version does not come with the tools ISO anymore. Might be the next challenge...

[nathanael-h]

I think you could use cd_files to provide Autounattend file for Windows in uefi mode.

See doc https://github.com/vatesfr/packer-plugin-xenserver/blob/main/docs/builders/iso/xenserver-iso.html.markdown#optional

cd_files (array of strings) - A list of files to place onto a CD that is attached when the VM is booted. This is most useful for unattended Windows installs, which look for an Autounattend.xml file on removable media. By default, no CD will be attached. All files listed in this setting get placed into the root directory of the CD and the CD is attached as the first CD device. Currently, no support exists for creating sub-directories on the CD. Wildcard characters (*, ?, and []) are allowed. Directory names are also allowed, which will add all the files found in the directory to the CD.