unable to enter commands into winedbg under muvm

[i509VCB]

After building wine according to the arm64ec instructions (detailed here: https://wiki.fex-emu.com/index.php/Development:ARM64EC) and running wine inside of muvm, trying to launch winedbg results in being unable to send commands to winedbg in a shell. Trying to press enter results in ^J appearing.

You might find this copr to be helpful for testing this issue: https://copr.fedorainfracloud.org/coprs/lacamar/wine-arm64ec/

This does not appear to be an issue with tmux, as trying to do this outside of tmux results in the same issue. I am using alacritty as my terminal.

dnf says I am using muvm 0.4.1.

Running wine outside of muvm does work, but most things don't work unless run inside muvm.

Video:

Screencast_20250914_195910.webm

[nrabulinski]

Out of curiosity, can you try running some random command like bash in muvm in one terminal first, then open a new terminal, open another muvm "session" and only then try to run winedbg, specifically in the second muvm you'll have open?

Sorry if I didn't explain it too well, but basically before running winedbg, try to already have muvm running in another terminal

[i509VCB]

Out of curiosity, can you try running some random command like bash in muvm in one terminal first, then open a new terminal, open another muvm "session" and only then try to run winedbg, specifically in the second muvm you'll have open?

Sorry if I didn't explain it too well, but basically before running winedbg, try to already have muvm running in another terminal

That is weird, but it does work. Hold on a moment, muvm doesn't seem to launch 2 guests?

[i509VCB]

I can't seem to get two terminals to connect to the same session (comment above is a red herring).

The first invocation (just using muvm python3) does get into muvm. Python does say the right uname is set:

>>> import os
>>> os.system("uname -a")
Linux verdigris 6.12.34 #1 SMP Thu Jun 26 12:45:10 CEST 2025 aarch64 GNU/Linux
0

But in another terminal muvm bash seems to never attach to muvm and continues running on the host per uname:

i509vcb@verdigris:~$ muvm bash
i509vcb@verdigris:~$ uname -a
Linux verdigris 6.16.4-402.asahi.fc42.aarch64+16k #1 SMP PREEMPT_DYNAMIC Tue Sep  2 13:45:43 UTC 2025 aarch64 GNU/Linux

Although my cursed workaround seems to be just spawn alacritty inside the muvm guest?

[nrabulinski]

Yeah, exactly. As I suspected, it works if you attach to an already-running session. This is a quirk of the difference in how the "root" tty is allocated and attached vs every other one.

This would be fixed if I ever got around to finishing up #157, which unifies the two paths.

[nrabulinski]

But in another terminal muvm bash seems to never attach to muvm and continues running on the host

Oh that's even weirder then. I haven't looked at muvm in a while since I'm not on asahi right now, but that's definitely either a regression or some upstream issue