Sample hello world application exit command CTRL+a not working in qemu_x86

[PriyadharsanLinumiz]

Describe the bug

Platform: Ubuntu 24.04.4 LTS

Command (CTRL+a) to exit the hello world application is not working, when built for qemu_x86

Regression

• This is a regression.

Steps to reproduce

1.Activate the venv
2. Go to zephy root
3. west build -b qemu_x86 samples/hello_world
4. west build -t run
5. Press CTRL+a

Relevant log output

Impact

Annoyance – Minor irritation; no significant impact on usability or functionality.

Environment

No response

Additional Context

No response

[github-actions[bot]]

Hi @PriyadharsanLinumiz! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[stephanosio]

Ctrl+a x?

[PriyadharsanLinumiz]

also tried this combination, same behaviour

[atsanak]

Ctrl+A is only QEMU’s escape prefix; the exit sequence is press/release Ctrl+A, then press x. It is not a simultaneous Ctrl+A+X chord.

If that still does nothing, the usual cause is that QEMU is not receiving an interactive TTY or an outer terminal multiplexer consumes the prefix:

1. Run west build -t run directly in an interactive terminal (not through redirected stdin, a background task, or a CI console).
2. Run it once with verbose output and verify the QEMU command contains a multiplexed stdio chardev such as -chardev stdio,...,mux=on plus -nographic. That is the configuration that enables the QEMU escape sequences.
3. If you are inside GNU Screen, its own prefix is Ctrl+A; use Screen’s “send literal Ctrl+A” sequence (Ctrl+A, then a), then press x. Also check IDE terminal keybindings that may consume Ctrl+A.
4. As a diagnostic, try Ctrl+A, then c to enter the QEMU monitor, followed by quit. If the monitor does not appear, the prefix is being intercepted before it reaches QEMU.
5. Ctrl+C should still terminate the foreground west/Ninja run as a fallback.

QEMU documents the mux escape keys here: https://www.qemu.org/docs/master/system/mux-chardev.html

This also explains why automated harnesses can report a completed Zephyr test suite while the run target remains resident: the guest finished, but the emulator still needs an interactive escape or an external timeout.