From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dor Laor Subject: Re: Pending signals prevent entry to the guest Date: Wed, 21 Jan 2009 10:05:37 +0200 Message-ID: <4976D751.4080706@redhat.com> References: <9780058.34741232510963338.JavaMail.root@mailserv1> Reply-To: dlaor@redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm To: Steven Stovall Return-path: Received: from mx2.redhat.com ([66.187.237.31]:60177 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1749667AbZAUIFV (ORCPT ); Wed, 21 Jan 2009 03:05:21 -0500 In-Reply-To: <9780058.34741232510963338.JavaMail.root@mailserv1> Sender: kvm-owner@vger.kernel.org List-ID: Steven Stovall wrote: > I posted about a week ago regarding a very different behavior with a host-side app vis a vis kvm-77 vs kvm-33. Pending signals (SIGIO and SIGALRM) never seem to be dequeued so that I never kvm_guest_enter()...it appears that only the dynticks alarm_timer gets enabled which only handles SIGALRM, while the rtc alarm_timer which handles SIGIO does not. I have tried to make sure both are enabled, but I still have perpetual pending signals...is this possible?? Or is there some corruption somewhere? > How many signal_exits do you see on kvm_stat? What's your host kernel version? It wasn't clean if you use dyn tick or rtc clock in qemu. Please post the command line. > Steven > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >