When the login step is called in a separate command after the guest has been provisioned, the connection seems to be stuck. No input or output is shown and it's not possible to disconnect from the guest. Steps to reproduce:

tmt run provision -h virtual
tmt run --last login

Seems the problem was introduced in d549bd3. @happz, any idea what might be the cause here?