uvt-kvm create ... && uvt-kvm wait ... && uvt-kvm ssh ... is inconvenient and repetitive

[Robie Basak]

This is a common use case. I propose: "uvt-kvm ssh --wait ...", to incorporate a default wait first. A shortcut could be: "uvt-kvm ssh -w ...".

This would save having to retype the guest name and --insecure (as long at that remains) all the time.

This leads to a question: should the ssh subcommand also accept all options that the wait subcommand does? I'd say no, since this increases complexity and I'm not sure how useful it would be. Scripts that use them could just call wait and then ssh, and that wouldn't really be any extra effort from a human.

[Robie Basak (racb)]

Some other ideas.

From Louis: uvt-kvm create --wait, to do the wait automatically.

Further ideas stemming from this: uvt-kvm create --login|-l, which will imply --wait and also ssh automatically.

[khb (khbkhb)]

slight variation, I find myself often using

uvt-kvm wait $DOMAIN && sleep 45 && uvt-kvm shh $DOMAIN

because I've got ssh configured to do X11 forwarding, and without the sleep, the initial ssh tends to not work as expected due to Xauth not yet being ready. 45s is probably much longer than necessary, uvt-kvm wait should be "long enough" so that reasonable use cases are covered.

[Robie Basak (racb)]

I object to arbitrary sleeps and would like to avoid them as much as possible because they cause cumulative delays in scripts.

You can adjust the wait script to do whatever you like. See --remote-wait-script in uvt-kvm(1). Enhancements to the default wait script shipped with uvtool are welcome, providing that they don't break existing common use cases or unnecessarily slow down users who don't want any additional delays.