I’m encountering an issue where an additional IP address is attached to a VM being built by Packer - this address appears at the point Packer runs the
Connecting to VNC over websocket…
and
Typing the boot command over VNC…
stage - so very early and no where where we have much if any control!
At this point the VM isn’t even up and no virtio drivers have been loaded - and so it isn’t ‘known’ by Windows but it’s the first listed IP address so that’s the one Packer tries to communicate on - so the build fails as communication is never established.
I’ve tried releasing and renewing an IP address in Windows during the build but Windows doesn’t know about the address at all so it doesn’t do anything useful. The VM shows as having 2 addresses from DHCP in Prism Central…
I’m all out of ideas! Any insight gratefully received!