From owner-freebsd-emulation@FreeBSD.ORG Mon Apr 6 20:54:01 2009 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03C301065873 for ; Mon, 6 Apr 2009 20:54:01 +0000 (UTC) (envelope-from kalinoj1@iem.pw.edu.pl) Received: from volt.iem.pw.edu.pl (volt.iem.pw.edu.pl [194.29.146.3]) by mx1.freebsd.org (Postfix) with ESMTP id B44528FC0A for ; Mon, 6 Apr 2009 20:54:00 +0000 (UTC) (envelope-from kalinoj1@iem.pw.edu.pl) Received: from hom.localnet (chello089079156006.chello.pl [89.79.156.6]) (Authenticated sender: kalinoj1) by volt.iem.pw.edu.pl (Postfix) with ESMTPSA id 18AEBA66644; Mon, 6 Apr 2009 22:53:57 +0200 (CEST) From: Jedrzej Kalinowski To: Juergen Lock Date: Mon, 6 Apr 2009 22:54:37 +0200 User-Agent: KMail/1.11.1 (Linux/2.6.29-gentoo-hom; KDE/4.2.1; x86_64; ; ) References: <200904032223.n33MNTiq019599@triton.kn-bremen.de> In-Reply-To: <200904032223.n33MNTiq019599@triton.kn-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200904062254.37824.kalinoj1@iem.pw.edu.pl> X-Virus-Scanned: clamav-milter devel-r5017-exp at volt.iem.pw.edu.pl X-Virus-Status: Clean Cc: freebsd-emulation@freebsd.org Subject: Re: Recent qemu and timers issue X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2009 20:54:01 -0000 Dnia sobota 04 kwietnia 2009 o 00:23:29 Juergen Lock napisa=C5=82(a): > In article you write: > >Hi all, > > > >When running FreeBSD 8-CURRENT system inside a qemu machine (from the > >latest port by nox@freebsd.org) I have strange timer problems in the > >virtual machine. > > What is the host running, also current? Yes, the host is also running current.=20 But the same host has no problem with older FreeBSD kernels on the guest, e= g.=20 =46reeSBIe 1.1 or FreeNAS (kernel v.6.4) > > >My logs and console are full of messages like this: > >calcru: runtime went backwards from 11248014678717988 usec to 119242 usec > >for pid 60 (ps) > > > >calcru: runtime went backwards from 11248014678921829 usec to 2516605 us= ec > >for pid 60 (ps) > >calcru: runtime went backwards from 7014844 usec to 6270851 usec for pid= 0 > >(kernel) > > > >It even happens for some processes to die inside qemu guest. > > Is this an smp host? You could try forcing qemu onto one cpu by > doing like: > cpuset -l 0 qemu ... > Yes, it's an smp host (8 cpus). But cpuset -l 0 qemu ... (also -clock=20 dynticks) didnt't help. > >I tried to use all possible timers using sysctl, where I have: > >TSC(800) HPET(900) ACPI-safe(850) i8254(0) dummy(-1000000) > >None of these helped. > > On the host or in the guest? > It's in the guest machine., where I tried these settings=20 One important thing I forgot to mention in my initial posting: When I run 'systat -vm 1' o the guest machine - it's almost fully loaded - = and=20 80% (or more) of it's cpu time is spent in interrrupt handling! This is als= o=20 not the case with older kernels. > [snip] > >I would greatly appreciate any help or a hint - where should I look for > >help on this issue. > > If none of these help you could also try the qemu list: > http://lists.nongnu.org/mailman/listinfo/qemu-devel > (I think you can still post without being subscribed, altho in that case > it may take a while for the post to get thru.) > > HTH, > Juergen At this moment it's very hard for me to judge if it's qemu or kernel issue.. Any thoughts? Thanks, J=C4=99drzej Kalinowski