Whenever we input a boot_command (to press a button in UEFI BIOS to start the attached disk) we get a failure;
==> xenserver-iso.win10: Step: Set SSH address to VM host IP
==> xenserver-iso.win10: Set host SSH address to '1.1.1.1.
==> xenserver-iso.win10: Unpausing VM 37249b69-da92-4042-ea5b-f54670b5c27a
==> xenserver-iso.win10: Waiting 5s for boot...
==> xenserver-iso.win10: Connecting to the VM console VNC over xapi via 1.1.1.1
==> xenserver-iso.win10: Making HTTP request to initiate VNC connection: CONNECT /console?uuid=ce5fd319-72b4-2b36-b773-5adb44507ef6 HTTP/1.0
==> xenserver-iso.win10: Host: 1.1.1.1
==> xenserver-iso.win10: Cookie: session_id=OpaqueRef:7996cbe2-0e1e-43c3-b780-f58c4d6f28d2
==> xenserver-iso.win10:
==> xenserver-iso.win10:
==> xenserver-iso.win10: Received response: HTTP/1.1 200 OK
==> xenserver-iso.win10: Connection: keep-alive
==> xenserver-iso.win10: Cache-Control: no-cache, no-store
==> xenserver-iso.win10:
==> xenserver-iso.win10:
==> xenserver-iso.win10: Error detecting local IP: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain`
It seems like it's trying to SSH to the host and gives up (certainly the intent could not be to SSH to a machine before it even has an OS installed). The ssh_username/password fields do not help and do not even seem to affect the behavior. If the boot_command is removed entirely and we use BIOS (or hit spacebar in bios ourselves) the entire build is fine.
Whenever we input a boot_command (to press a button in UEFI BIOS to start the attached disk) we get a failure;
It seems like it's trying to SSH to the host and gives up (certainly the intent could not be to SSH to a machine before it even has an OS installed). The ssh_username/password fields do not help and do not even seem to affect the behavior. If the boot_command is removed entirely and we use BIOS (or hit spacebar in bios ourselves) the entire build is fine.