-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add a "QEMU Console" button in the toolbar for QEMU VMs, link to monitor. #3522
Comments
To avoid confusion for regular users, it could be hidden by default, but an optional button to add to the toolbar in prefs. |
I disagree with this philosophy. It's one of the most frustrating things dealing with the Linux community is that because more advanced options exist, people will just dismiss UX issues since "you can just do this in the terminal".
There's plans to support PTY interface for serial forwarding. I can make QEMU monitor as an option for the serial port. |
Your plans sound like a great option for macOS; how would that work for i*OS users? I'm thinking that linking it in to your debug log would also be useful (and doable by just sending monitor commands in the background and emitting the results to STDOUT, such as the QEMU hardware configuration) |
You can open a TCP port on iOS and use a telnet client. |
I guess we can close this one as "won't fix" unless you want to change the title to "add QEMU monitor as an option for the serial port." |
@osy is there an open issue about the PTY interface? |
Superseded by #3546 |
It would be great to expose the QEMU monitor for more advanced users.
Since this provides direct access to the existing QEMU interface for disk management, debugging, VM snapshots, etc. it would enable UTM users to use advanced features even if they're not being presented as options in the default UTM UI. It would also mean the QEMU monitor documentation would be directly applicable, so UTM wouldn't have to maintain its own documentation for the feature.
There's currently over a dozen feature requests in the Issue tracker that would instantly be resolved with this feature (direct people to use existing commands in monitor), plus others that could be properly debugged with the monitor easily available. Following implementation, feature requests could switch to exposing specific monitor features in the UI, rather than people making requests for features similar to what's already available in QEMU but hidden from the UI.
The text was updated successfully, but these errors were encountered: