qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] QEMU for Windows - UI status


From: Stefan Weil
Subject: [Qemu-devel] QEMU for Windows - UI status
Date: Sat, 10 Dec 2016 15:33:08 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0

This is a status summary for UI support in QEMU for Windows.

Available user interfaces
-------------------------

* curses
* SDL 1.2
* SDL 2.0
* GTK without VTE
* VNC

Status curses
-------------

It is supported, but I don't have any test results as I nearly
never use it. It does not support graphics, so its use is very
limited.

Status SDL 1.2
--------------

I dropped using SDL 1.2 for QEMU 2.8, so I have no new test results.
With QEMU 2.7 SDL 1.2 works, but the redirection of STDOUT and STDERR
to files confuses users ("crash without any message") and does not
work because of missing rights for typical installations.

Status SDL 2.0
--------------

I started testing with SDL 2.0 today. A default build for Windows
is not usable, because QEMU terminates immediately with an error
message: "Fatal Error: Out of memory - aborting" (even if running
without -sdl).

This is caused by main being mapped to SDL_main and probably a
mismatch between QEMU (compiled with TCHAR = 1 byte) and SDL2
(compiled with TCHAR = 2 bytes). It can be fixed by defining
SDL_MAIN_HANDLED before including SDL.h and undefining main.

Fixing main is not sufficient: booting the 386 BIOS is extremely
slow, obviously with threads waiting for each other, maybe deadlocks.
Keyboard and mouse input seems to help a little bit.

Status GTK without VTE
----------------------

There is no VTE for Windows, and I see no chance to port the VTE code
for that platform.

Without VTE, QEMU's monitor window does not have a history. Scrolling
in lengthy output (help command) is not possible. This can be
reproduced on Linux, too, by disabling VTE support.

In addition, I got this report from Howard (cc'ed):

These are the issues I encountered with qemu-system-ppc.exe in the GTK gui:
-Mouse tracking is not exact.The mouse in guest Mac OS/Mac OSX is
faster than the host mouse.
-Input grab allows the mouse to travel outside the guest window.
-Double click speed is set so fast it is almost impossible to achieve
a double click.
-It requires constant moving of the mouse to achieve boot times
comparable to SDL, otherwise boot is extremely slow.

AFAIK tablet mode should give better (good?) results, but I don't
think it will fix the deadlock issues which slow down operations.

I know that there are keyboard issues with GTK (even on Linux)
when using a non English keybords (Umlauts, AltGr key on
German keyboard).

Status VNC
----------

I use it rarely, but it seems to work. The VNC code still needs
surprisingly many commits. Maybe code stability could be improved
by removing most of the code in QEMU and replacing it by libvnc.

Summary
-------

Most QEMU user interfaces have problems on Windows.

It looks as if the old SDL 1.2 is still a good option for Windows.
VNC might be another good choice.

Comments and fixes are welcome. For 2.8, I documented the SDL 2 problem,
but I won't send last minute fixes.

Regards
Stefan




reply via email to

[Prev in Thread] Current Thread [Next in Thread]