From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [ANNOUNCE] kvm-43 release Date: Sat, 22 Sep 2007 08:36:48 +0200 Message-ID: <46F4B800.20408@qumranet.com> References: <46F358D2.9000009@qumranet.com> <46F3E1E7.7010602@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Gerd Hoffmann Return-path: In-Reply-To: <46F3E1E7.7010602-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Gerd Hoffmann wrote: > Avi Kivity wrote: > >> Only one fix, but an important one. It fixes booting of newer Linux >> versions, which experienced disk and keyboard problems without >> -no-kvm-irqchip. >> >> As usual, if you have an issue please try with -no-kvm-irqchip and report. >> > > Updated from -41. Now my libkvm-using-tool's > kvm_callbacks->try_push_interrupts() callback isn't called any more. > Hmm. Guess due to the lapic/irqchip changes. Are there any additional > initializations I have to do now? > > As there isn't any real pic-like hardware emulated maybe using > try_to_push_interrupts is a bad idea anyway and I should better move the > code (checks state and calls kvm_inject_irq() if needed) to the > pre_kvm_run() callback? > > hints anyone? > You can call kvm_disable_irqchip_creation() to kill in-kernel pic and friends. (the logic is inverted -- the function should be kvm_enable_irqchip_creation() so that this problem would not occur) -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/