action #60758
Updated by okurz almost 5 years ago
## Motivation As a test reviewer of tests running on remote backends I do not want to be lost what is the source of the problem when the only thing I see is error messages from xterm. Also see See #60539 . Xvnc is used in more and more tests where we connect to a remote hypervisor to run VMs on and establish connections between the VM, the hypervisor and the openQA worker instance. The feedback in case of failures can be improved and we do not have this setup covered in os-autoinst tests so making changes is risky. ## Suggestions * Create tests using any Xvnc based backend, not qemu, which at least start up the complete stack and ensure it being able to execute tests, e.g. only simulate a VM, just work with the xterm-console that is started