Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

platform/qemu: add 'qemu-vnc' option #540

Merged
merged 1 commit into from
Jul 16, 2024
Merged

Conversation

tormath1
Copy link
Contributor

This option can be set to 0, 1, 2, etc. to set a QEMU VNC server on resp. port 5900, 5901, 5902, etc.

QEMU tests are running in a dedicated network namespace, to access the VNC server, you need to proxy the request.

Example:

mkfifo reply
ncat -kl 12800 < reply | sudo nsenter -t "${QEMUPID}" -n ncat localhost 5900 > reply
rm reply

Using any VNC client, you can access the VNC session on port 12800.

This can be useful when debugging booting issue (UEFI).

This option can be set to 0, 1, 2, etc. to set a QEMU VNC server on resp.
port 5900, 5901, 5902, etc.

QEMU tests are running in a dedicated network namespace, to access the
VNC server, you need to proxy the request.

Example:
```
mkfifo reply
ncat -kl 12800 < reply | sudo nsenter -t "${QEMUPID}" -n ncat localhost 5900 > reply
rm reply
```

Using any VNC client, you can access the VNC session on port 12800.

This can be useful when debugging booting issue (UEFI).

Signed-off-by: Mathieu Tortuyaux <[email protected]>
@tormath1 tormath1 self-assigned this Jul 16, 2024
@tormath1 tormath1 requested a review from a team July 16, 2024 09:18
@tormath1 tormath1 merged commit 1adf266 into flatcar-master Jul 16, 2024
2 checks passed
@tormath1 tormath1 deleted the tormath1/vnc branch July 16, 2024 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants