It would be useful to have the contents of the guest VM's journalctl as part of the gathered info.
Motivation: journalctl contains much info that may not be available elsewhere, for example - networking team debugged a recurring flakiness in many of our tests, which eventually was found to be a result of IP conflicts with IT components in other clusters that share the same domain. The root cause was eventually found by accessing the journalctl of such VM, but because this was a result of a flakiness, we had to repeat the tests many times until hitting the failure while the VM was up. Having the joutnalctl attached to the jenkins job where it failed (via the must-gather output) would have saved a lot of precious debugging time.
Thank you