From owner-freebsd-emulation@FreeBSD.ORG Fri Apr 3 07:35:49 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 C12E7106564A for ; Fri, 3 Apr 2009 07:35:49 +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 845DD8FC1F for ; Fri, 3 Apr 2009 07:35:49 +0000 (UTC) (envelope-from kalinoj1@iem.pw.edu.pl) Received: by volt.iem.pw.edu.pl (Postfix, from userid 80) id D4E22A666EA; Fri, 3 Apr 2009 09:35:45 +0200 (CEST) To: MIME-Version: 1.0 Date: Fri, 03 Apr 2009 09:35:45 +0200 From: Jedrzej Kalinowski Message-ID: X-Sender: kalinoj1@iem.pw.edu.pl User-Agent: RoundCube Webmail/0.2-beta Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Subject: 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: Fri, 03 Apr 2009 07:35:50 -0000 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. 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 usec 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. 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. What's more I cannot corelate this with kern.hz value set for the system. I tried to set it to the same value as host machine, bigger and smaller one. It's not a kqemu issue, happens also with -no-kqemu switch. I've already posted this issue on freebsd-current some time ago, but unfortunately noone showed interest in it.. (http://docs.freebsd.org/cgi/mid.cgi?3cd67c0d967b2464a4b40bd85582bf88) I would greatly appreciate any help or a hint - where should I look for help on this issue. Cheers, Jędrzej Kalinowski