From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Lieven Subject: disable clocksource=kvm-clock Date: Tue, 01 Jun 2010 15:12:35 +0200 Message-ID: <4C050743.3030603@dlh.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: qemu-devel@nongnu.org, kvm@vger.kernel.org Return-path: Received: from zion.dlh.net ([91.198.192.1]:38165 "EHLO mail.dlh.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753030Ab0FANMi (ORCPT ); Tue, 1 Jun 2010 09:12:38 -0400 Sender: kvm-owner@vger.kernel.org List-ID: hi, is it possible to avoid detection of clocksource=kvm_clock in a linux guest by patching the qemu-kvm binary? i would like to be able to avoid a guest detecting kvm-clock until bug #584516 is fixed without modifying all guest systems and reverting that later. thanks, peter From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=42593 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OJRGo-000425-FH for qemu-devel@nongnu.org; Tue, 01 Jun 2010 09:12:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OJRGn-0007GB-9X for qemu-devel@nongnu.org; Tue, 01 Jun 2010 09:12:38 -0400 Received: from zion.dlh.net ([91.198.192.1]:59111 helo=mail.dlh.net) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OJRGn-0007Fy-2d for qemu-devel@nongnu.org; Tue, 01 Jun 2010 09:12:37 -0400 Message-ID: <4C050743.3030603@dlh.net> Date: Tue, 01 Jun 2010 15:12:35 +0200 From: Peter Lieven MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] disable clocksource=kvm-clock List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, kvm@vger.kernel.org hi, is it possible to avoid detection of clocksource=kvm_clock in a linux guest by patching the qemu-kvm binary? i would like to be able to avoid a guest detecting kvm-clock until bug #584516 is fixed without modifying all guest systems and reverting that later. thanks, peter