From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FbfB0-0003Mz-6D for qemu-devel@nongnu.org; Thu, 04 May 2006 10:51:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FbfAx-0003Ma-Vh for qemu-devel@nongnu.org; Thu, 04 May 2006 10:51:33 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FbfAx-0003MW-Rt for qemu-devel@nongnu.org; Thu, 04 May 2006 10:51:31 -0400 Received: from [66.249.82.194] (helo=wx-out-0102.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FbfBa-0002ZO-Ka for qemu-devel@nongnu.org; Thu, 04 May 2006 10:52:10 -0400 Received: by wx-out-0102.google.com with SMTP id h26so334622wxd for ; Thu, 04 May 2006 07:51:31 -0700 (PDT) Message-ID: <170581c20605040751y5118c2en360b67901b2b27a5@mail.gmail.com> Date: Thu, 4 May 2006 07:51:29 -0700 From: "Thomas Han" Subject: Re: [Qemu-devel] QEMU 0.8.1 In-Reply-To: <46d6db660605040531q3a602d03yd8f25b23823e1424@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_30728_26808148.1146754289360" References: <4459165F.7050605@bellard.org> <46d6db660605040513y3534fecdr5ffe4e632108e413@mail.gmail.com> <46d6db660605040524h1d5f1484mb3a4cf1e343d6984@mail.gmail.com> <46d6db660605040531q3a602d03yd8f25b23823e1424@mail.gmail.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_30728_26808148.1146754289360 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, For what it's worth. I have also seen this "invisible wall" problem with m= y mouse for a few weeks off the CVS build too. Since 0.8.1 came out yesterday, Instead of using CVS build, I'm now running Qemu 0.8.1 + kqemu-1.3.0pre6. My host OS is FC5 and I'm running XP inside it. Thanks, Thomas On 5/4/06, Christian MICHON wrote: > > qemu 0.8.0 does not show this invisible barrier issue. > if this is worth anything, I use SDL 1.2.9. > > If someone can reproduce the issue also on linux hosts, > there could be a lead. > > On 5/4/06, Christian MICHON wrote: > > I removed manually vnc_display_init, and this is not the culprit... > > I'll check anyway versus qemu-0.8.0... > > > -- > Christian > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > ------=_Part_30728_26808148.1146754289360 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,

For what it's worth.  I have also seen this "invisible= wall" problem with my mouse for a few weeks off the CVS build too.
Since 0.8.1 came out yesterday, Instead of using CVS build, I'm now ru= nning Qemu=20 0.8.1 + kqemu-1.3.0pre6.  My host OS is FC5 and I'm running XP inside = it.

Thanks,
Thomas

On 5/4= /06, Christian MICHON < christian.michon@gmail.com> wrote:
qemu 0.8.0 does not show this invisible barr= ier issue.
if this is worth anything, I use SDL 1.2.9.

If someone can repro= duce the issue also on linux hosts,
there could be a lead.

On 5/4= /06, Christian MICHON <chr= istian.michon@gmail.com > wrote:
> I removed manually vnc_display_init, and this is no= t the culprit...
> I'll check anyway versus qemu-0.8.0...
>
= --
Christian


_______________________________________________
Qemu-devel mailing list
Qem= u-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
<= /blockquote>

------=_Part_30728_26808148.1146754289360--