I’m still debugging my sys-gui-gpu VM, and I’d like to interact with it a bit while it’s running, while it still has not managed to start the amdgpu driver. /var/log/xen/console/guest-sys-gui-gpu.log shows that despite the driver woes the VM is still running, showing a getty prompt and kernel console traces.
If I try to open a plain old shell with qvm-run -p sys-gui-gpu 'bash -i', I just don’t get any output (my ^C gets highlighted in red as the shell output should, but I just don’t get to interact with any process in the VM).
xl console, for its part, refuses with Unable to attach console (maybe because the console is already redirected to a file?)
… and I don’t get any clue in the various logfiles.
This command does not include a man page or a --help output, but launching it without arguments displays the help:
$ qvm-console-dispvm
Usage: /usr/bin/qvm-console-dispvm [--autostart] [--] vmname
Connects to VM console throught DispVM using the qubes.ShowInTerminal RPC service.
With --autostart, start the VM first.
Now it appears the usability of that user shell is a bit limited. With --passio not providing a tty to the VM shell, I can launch individual root commands with sudo, but cannot get an interactive root shell, and I don’t have any shell history – sad thing having to cut/paste/edit – but at least I do have that shell