QA » openQA Project

Description¶

On non-qemu backend openQA setups, take s390x-kvm as an example, when I try to debug some issue with developer mode,
we can get the information from openqa web UI like:
You might be able to connect to the SUT at worker32.oqa.prg2.suse.org:5994 via VNC with shared mode enabled (eg. vncviewer workerxx.xx.org:5994 -Shared for TigerVNC).

However, it can not work for s390x-kvm setup since it is remote access. we may need to access the setup with below methods:

1. ssh to vm directly
2. vncviewer to access with ip addr of s390x-SUT with right port
3. accss to s390x-SUT and use virsh console command to access the serial terminal/console

Please see attached file.

Suggestion¶

1. OpenQA can show test the right VNC port or right method to access the setup
2. For no qemu backend, openQA may show some warning messages that the VNC access information is not usable.