boot_command appears to lose vnc connection on guest reboot

[kevemueller]

I have a boot_command that spans a guest reboot. Basically it is performing an installation, restarting the machine, awaiting it to come back up and continuing after it initialized its state.
The work cannot be done before reboot as the environment for that is not yet set-up.

Despite generous <wait> applied, the boot_command cannot complete. One indication that it is VNC related is that the console is no longer locked exclusively in XO, meaning while packer is still typing, the rebooted guest's console is already visible in XO.
A similar packer configuration against vsphere runs through, i.e. there the boot_command is continued with the rebooted guest.

[AtaxyaNetwork]

Hi,

I had this issue too when I tried to build a VyOS box.

I check the code, and saw it was "Heavily borrowed" from QEMU builder.
Then, I check the QEMU builder code, and saw it was rework a few years back: hashicorp/packer-plugin-qemu@82fd7e2

I don't want to promise everything, but since I have the same "bug" (actually, I was thinking it was "normal"), I want to give a try to reimplement this part of the code. (and I think it will resolve #133 too)

I'm not a dev (more a sys/net admin girl), so I will probably ask for help and my code will need some testing/review/love.