Steven Stovall wrote:
Can you please explain why dyn or rtc are not the right alarm_timers? My host is linux-2.6.24.
Both options should be fine. I asked for cmd line and kvm_stat output.
----- Original Message -----
From: "Dor Laor" <dlaor@xxxxxxxxxx>
To: "Steven Stovall" <sstovall@xxxxxxxxxxxx>
Cc: "kvm" <kvm@xxxxxxxxxxxxxxx>
Sent: Wednesday, January 21, 2009 12:05:37 AM GMT -08:00 US/Canada Pacific
Subject: Re: Pending signals prevent entry to the guest
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
