From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LUor3-0006tH-Lk for qemu-devel@nongnu.org; Wed, 04 Feb 2009 16:00:17 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LUor1-0006su-Uq for qemu-devel@nongnu.org; Wed, 04 Feb 2009 16:00:17 -0500 Received: from [199.232.76.173] (port=58919 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LUor1-0006sr-PK for qemu-devel@nongnu.org; Wed, 04 Feb 2009 16:00:15 -0500 Received: from fg-out-1718.google.com ([72.14.220.156]:47475) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LUor1-0000Rr-B0 for qemu-devel@nongnu.org; Wed, 04 Feb 2009 16:00:15 -0500 Received: by fg-out-1718.google.com with SMTP id e21so1408091fga.8 for ; Wed, 04 Feb 2009 13:00:13 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <4989B280.8070803@earthlink.net> References: <49876B4C.9090806@bttr-software.de> <498773B6.7060301@codemonkey.ws> <4987F7F1.2040104@redhat.com> <49883914.2030904@codemonkey.ws> <20090203132841.GB15613@redhat.com> <20090204122804.GA8111@shareable.org> <4989B280.8070803@earthlink.net> Date: Wed, 4 Feb 2009 22:00:13 +0100 Message-ID: <68676e00902041300o731925e3jd0c523dbbb87036a@mail.gmail.com> Subject: Re: [Qemu-devel] QEMU SVN on Windows 2000 :-( From: Luca Tettamanti Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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 On Wed, Feb 4, 2009 at 4:21 PM, Robert Reif wrote: > Jamie Lokier wrote: >> >> years later. Does Qemu run on Linux 2.4? > > QEMU runs on RedHat 9 which is 2.4.20 but only with this > patch (otherwise it just hangs at startup): > > --- vl.c (revision 6510) > +++ vl.c (working copy) > @@ -1008,8 +1008,8 @@ > static struct qemu_alarm_timer alarm_timers[] = { > #ifndef _WIN32 > #ifdef __linux__ > - {"dynticks", ALARM_FLAG_DYNTICKS, dynticks_start_timer, > - dynticks_stop_timer, dynticks_rearm_timer, NULL}, > +// {"dynticks", ALARM_FLAG_DYNTICKS, dynticks_start_timer, > +// dynticks_stop_timer, dynticks_rearm_timer, NULL}, > /* HPET - if available - is preferred */ > {"hpet", 0, hpet_start_timer, hpet_stop_timer, NULL, NULL}, > /* ...otherwise try RTC */ You can override the order of the timers with -clock, e.g.: -clock hpet,rtc,unix will try first hpet, then rtc and unix (ignoring dynticks). It should hang though, can you see if dynticks_rearm_timer gets called? Luca