From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip Date: Wed, 02 Feb 2011 15:14:26 +0200 Message-ID: <4D4958B2.4070709@redhat.com> References: <4D484A9B.9040604@siemens.com> <20110202115537.GE14984@redhat.com> <4D4946F7.1070702@siemens.com> <20110202123532.GF14984@redhat.com> <4D4952FA.8020300@siemens.com> <4D49569F.6060207@redhat.com> <4D495784.7050004@siemens.com> <20110202131103.GG14984@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , kvm , qemu-devel To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22537 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751613Ab1BBNOy (ORCPT ); Wed, 2 Feb 2011 08:14:54 -0500 In-Reply-To: <20110202131103.GG14984@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 02/02/2011 03:11 PM, Gleb Natapov wrote: > On Wed, Feb 02, 2011 at 02:09:24PM +0100, Jan Kiszka wrote: > > On 2011-02-02 14:05, Avi Kivity wrote: > > > On 02/02/2011 02:50 PM, Jan Kiszka wrote: > > >>>> > > >>> Opps, -smp 1. With -smp 2 it boot almost completely and then hangs. > > >> > > >> Ah, good (or not good). With Windows 2003 Server, I actually get a Blue > > >> Screen (Stop 0x000000b8). > > > > > > Userspace APIC is broken since it may run with an outdated cr8, does > > > reverting 27a4f7976d5 help? > > > > > > > -ECOMMITNOTFOUND, neither in qemu-kvm nor upstream. > > > This is kernel commit, but it is too old. I am pretty sure userspace irq > chip worked back then. I have memories of it failing autotest, but the conclusion was that the commit did not cause the problem, simply enlarged the window in which it could happen. -- error compiling committee.c: too many arguments to function