Machines: No ability to add consoles to existing VMs

[andreasn]

Page: Machines

During the latest round of usability testing, we found that 8 out of 11 users had issues figuring out what caused performance issues on a VM. One of the things almost all of them tried was connecting to the VM via the console, but it did not work. This is most likely because there was no session to connect to for those VMs. @KKoukiou suggested we should add that ability, and @marusak added that "maybe as we do in docker/podman. If there is TTY, connect to it, otherwise create a new session and connect to it"

[garrett]

@andreasn mentioned this on IRC:

Since we're moving VMs into their own detailed pages, that would free up what we can do with the console. We could, for example, switch console types to tabs (which we couldn't before, as it was already in tabs in an expanded list) and then all VMs would have all the types of consoles available. If they don't have a certain type of console active in the XML definition, Cockpit could have an empty state with a button to create that type of connection.

For example:

---

Graphical | Serial | Local

VNC has not been enabled on this VM
[ Enable VNC ]

---

Graphical | Serial | Local

Connected to Foo
Escape character is ^]

---

Graphical | Serial | Local

Instructions go here for how to connect locally

---

[KKoukiou]

Duplicate of #553