From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55130) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V3uhJ-0004U4-JB for qemu-devel@nongnu.org; Mon, 29 Jul 2013 17:09:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V3uhC-0003Th-AY for qemu-devel@nongnu.org; Mon, 29 Jul 2013 17:09:41 -0400 Received: from e8.ny.us.ibm.com ([32.97.182.138]:52498) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V3uhC-0003Su-2C for qemu-devel@nongnu.org; Mon, 29 Jul 2013 17:09:34 -0400 Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Mon, 29 Jul 2013 22:09:33 +0100 Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id C4DD7C90045 for ; Mon, 29 Jul 2013 17:09:28 -0400 (EDT) Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r6TL9Udl33030284 for ; Mon, 29 Jul 2013 17:09:30 -0400 Received: from d01av05.pok.ibm.com (loopback [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r6TL9TSn016920 for ; Mon, 29 Jul 2013 17:09:29 -0400 From: Anthony Liguori In-Reply-To: <51F6D388.9090406@weilnetz.de> References: <51F6927E.5040202@weilnetz.de> <871u6htf5r.fsf@codemonkey.ws> <51F6B1FC.7060707@weilnetz.de> <87wqo9i4c1.fsf@codemonkey.ws> <51F6C218.5060608@weilnetz.de> <51F6D1BE.1070707@suse.de> <51F6D388.9090406@weilnetz.de> Date: Mon, 29 Jul 2013 16:09:26 -0500 Message-ID: <8761vt8455.fsf@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [BUG] GTK terminal is broken List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil , Andreas =?utf-8?Q?F=C3=A4rber?= Cc: qemu-devel Stefan Weil writes: > Am 29.07.2013 22:34, schrieb Andreas F=C3=A4rber: >> Am 29.07.2013 21:27, schrieb Stefan Weil: >>> Am 29.07.2013 20:55, schrieb Anthony Liguori: >>>> Stefan Weil writes: >>>> >>>>> Am 29.07.2013 20:05, schrieb Anthony Liguori: >>>>>> Stefan Weil writes: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> maybe most developers will already have noticed that the terminal o= utput >>>>>>> in QEMU's GTK user interface is broken. As far as I know, it never = worked, >>>>>>> but as there are working alternatives, I did not care much and forg= ot to >>>>>>> report the issues. >>>>>>> >>>>>>> See these snapshots which show the problems with QEMU's GTK termina= ls: >>>>>>> >>>>>>> http://qemu.weilnetz.de/test/bugs/qemu-gtk-demo1.png >>>>>>> >>>>>>> Here the first line of the QEMUmonitor is only partially visible. >>>>>>> Tested with Cygwin/X on W64 host, QEMU running on Debian Linux. >>>>>>> Other X servers (e.g. native X on Debian Linux) don't show this >>>>>>> problem. >>>>>> It's a GTK/Cygwin/X bug. >>>>>> >>>>>> We use a vbox without anything particularly fancy happening. Looks = like >>>>>> something is calculating layout incorrectly. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Anthony Liguori >>>>> I miss a comment on the more important next two points. >>>>> They are _not_ related to Cygwin / X. >>>>> >>>>> Do you investigate them? >>>> What you're seeing has always existed and is not GTK specific. There = is >>>> not flow control on the outgoing side of serial emulation. Data will >>>> get dropped. >>>> >>>> My guess is that your system is sufficiently slow and overloaded that >>>> it's happening a lot for you. >>>> >>>> Regards, >>>> >>>> Anthony Liguori >>> If it were as simply as that, that would be fine, but alas, >>> it isn't. Even fast servers without any load show dropped >>> characters. There are dropped characters for QEMU's >>> monitor window (Alt-ctrl-2) and for Malta's line display >>> (Alt-Ctrl-5). Neither of these two should suffer from missing >>> flow control. >>> >>> And even a current X.Org on Ubuntu shows the first bug >>> (crippled first line) here, so it is not Cygwin / X specific. >> FWIW I've been seeing similar garbled-Gtk-output issues on openSUSE 12.3 >> but didn't investigate further. -monitor stdio has so far not failed me >> on the same system by comparison. >> >> One reproducible test case was the openrisc kernel that Jia provided >> recently. >> >> Regards, >> Andreas > > Maybe the problems only occur with TCG, but not with KVM. > That might explain why I get them more often than Anthony :-) > > Up to now, I did not try GTK terminals with KVM because my > typical test scenario uses MIPS or ARM boards on Intel hosts. x86 vs. other will come into play too. The serial driver for x86 has some basic backoff logic. I suspect others don't. My guess why you don't see this on -serial stdio is that it probably is using synchronous I/O. Regards, Anthony Liguori > > Regards, > Stefan