qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 0/6] fix w32 sockets


From: Stefan Weil
Subject: Re: [Qemu-devel] [PATCH 0/6] fix w32 sockets
Date: Wed, 21 Mar 2012 00:32:41 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120207 Iceowl/1.0b1 Icedove/3.0.11

Am 20.03.2012 10:49, schrieb Paolo Bonzini:
The w32 main loop has been mostly broken by the introduction of the
glib main loop. glib's g_poll does not use sockets on w32, so we
need a separate approach.

Patch 1 is a simple cleanup that is needed later in the series.

Patch 2 and patch 3 completely separate the way the main loop waits
on POSIX and w32 systems, and drop glib source handling from the w32
main loop.

Patch 4 fixes a longstanding bug in how sockets are handled, also
simplifying the code in the process. On top of this simplification,
patch 5 starts using g_poll in the w32 main loop and patch 6 adds
back glib source handling.

I didn't test this in the conditions explained in bug 916720, but I
tested both a TCP monitor and an stdio monitor and both work (under
Wine that is).

Stefan, can you please take care of shepherding the patches in
(pinging etc.)?

Hi Paolo,

it's really great that you addressed this main loop issue.

I tried to run an ARM system emulation for Raspberry Pi recently
and had much problems because QEMU was freezing very soon.

My host is Windows 7 (64 bit) running 32 and 64 bit versions
of QEMU with SDL. See https://bugs.launchpad.net/qemu/+bug/954099
for the command line and images.

A few seconds after start, QEMU freezes when I select screen 1 ("vga")
with the mouse (no more screen updates, no reaction on keyboard
input or window events).

If a switch to screen 3 (serial console 1) very fast after, I get
the message that the Linux kernel is uncompressed. It is also possible
to switch to screen 1 and watch the kernel boot messages, but it
freezes later.

Your patch series does not fix this, although I had expected that
it would, because I already noticed the problem with select. :-(

So we still have a problem to find.

Regards,

Stefan




reply via email to

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