Hyperkit's go api could not create console on stdio.

Could not create console on stdio with ConsoleStdio or StdioInteractiveConsole

Case 1. StdioInteractiveConsole

If I set the value of Serial.InteractiveConsole to StdioInteractiveConsole to create console on stdio, it return an error:
If StdioInteractiveConsole is set, stdio must be a TTY.

Unlike the description of the error, this error occurs when isTerminal() condition returns true. That is, although stdio is a tty, error occurs.

if isTerminal(os.Stdout) {
  return errors.New("If StdioInteractiveConsole is set, stdio must be a TTY")
}

Case 2. ConsoleStdio

If I set the value of Hyperkit.Console (without Serial) field to ConsoleStdio and call run(), an error occurs: exec: Stdout already set.

With stdio console, cmd.Stdout is set to os.Stdout (cmd.Stdout = os.Stdout). But the next line, cmd.StdoutPipe() method is called and the method return error when cmd.Stdout is not nil.

Start by tracing the Go API paths for StdioInteractiveConsole and ConsoleStdio into run(), then inspect the isTerminal(os.Stdout) check and the subsequent StdoutPipe() call. Reproduce both cases with stdio attached to a TTY and confirm that the TTY case no longer returns the incorrect error and ConsoleStdio no longer reports "exec: Stdout already set."