From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: smp guest questions Date: Wed, 17 Jun 2009 12:38:59 +0400 Message-ID: <4A38ABA3.2010401@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: KVM list Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:43576 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751068AbZFQIi7 (ORCPT ); Wed, 17 Jun 2009 04:38:59 -0400 Sender: kvm-owner@vger.kernel.org List-ID: After seeing words from Avi about that smp guests are ok now, I descided to try. And immediately got a few questions. Running on a Phenom 9750 machine (PhenomI), AMD780G chipset. Host is 2.6.29 x86-64, qemu-kvm 0.10.5, guests are linux with kvm paravirt bits enabled, also dynticks (on both host and guest). When booting a 2-CPU guest, I see in dmesg: PM-Timer running at invalid rate: 200% of normal - aborting. and indeed, in available_clocksource there's no pmtimer. Should I be concerned? It does not look healthy. Some time later, I see stuff like: hrtimer: interrupt too slow, forcing clock min delta to 47210997 ns Which reminds me issues I had with broken hpet (time goes back-n-forth with similar messages shown in dmesg, but about hpet not hrtimer). Also does not look healthy. I haven't seen either of the two messages above on any of single-processor guests so far, at least with recent kernels and kvm userspace, only on smp (2 cpu for now). Thanks! /mjt