From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HWc0s-0005jW-DP for qemu-devel@nongnu.org; Wed, 28 Mar 2007 13:32:46 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HWc0p-0005iE-TV for qemu-devel@nongnu.org; Wed, 28 Mar 2007 13:32:45 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HWc0p-0005iB-Mp for qemu-devel@nongnu.org; Wed, 28 Mar 2007 12:32:43 -0500 Received: from wr-out-0506.google.com ([64.233.184.237]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HWbyK-0005pJ-T1 for qemu-devel@nongnu.org; Wed, 28 Mar 2007 13:30:09 -0400 Received: by wr-out-0506.google.com with SMTP id i20so3313390wra for ; Wed, 28 Mar 2007 10:30:08 -0700 (PDT) Message-ID: <9a158e2e0703281030u595ed25dm973bb6ec4e0cbafe@mail.gmail.com> Date: Wed, 28 Mar 2007 10:30:07 -0700 From: "Kyle Hubert" Subject: Re: [Qemu-devel] virtual machine halting and loosing connections In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9a158e2e0703271634x3b806b7ahe070aae2ea8a9631@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: balrogg@gmail.com, qemu-devel@nongnu.org On 3/27/07, andrzej zaborowski wrote: > On 28/03/07, Kyle Hubert wrote: > > I've been looking online, but I can't say that I have found the answer > > to this yet. > > > > When using QEMU, I've noticed that if I switch away to a different > > virtual desktop on the host OS's WM, then QEMU stops what it is doing. > > It's really clear when it's in the middle of a boot, but it always > > occurs. This causes havoc since I'm using qemu as an ssh client and > > the server I'm connecting to drops me for inactivity. This doesn't > > matter if I use keepalive or not. > > Just confirming that I'm seeing the same thing, and it's not a recent > problem because I remember it happening in 0.7.2 and earlier. Just to let you and the list know, I downgraded to a 32bit kernel and it seems to have sorted itself out. Are you running on x86_64? -Kyle