From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgam4-0003gj-Sn for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:56:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgalz-0003fW-Pb for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:56:04 -0400 Received: from [199.232.76.173] (port=46537 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgalz-0003fT-JM for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:55:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57537) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mgalz-0005gn-16 for qemu-devel@nongnu.org; Thu, 27 Aug 2009 04:55:59 -0400 Message-ID: <4A964A1A.90604@redhat.com> Date: Thu, 27 Aug 2009 10:55:54 +0200 From: Gerd Hoffmann MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 2/2] Route IOAPIC interrupts via ISA bus References: <1249836296-13288-1-git-send-email-avi@redhat.com> <1249836296-13288-3-git-send-email-avi@redhat.com> <4A955CB4.4080205@redhat.com> <4A955D6A.9060804@redhat.com> <4A95633E.7060703@redhat.com> <20090826190944.GD11762@redhat.com> <4A963856.2040301@redhat.com> <20090827075728.GJ30093@redhat.com> <20090827081832.GA22631@shareable.org> In-Reply-To: <20090827081832.GA22631@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jamie Lokier Cc: qemu-devel@nongnu.org, Gleb Natapov , Avi Kivity On 08/27/09 10:18, Jamie Lokier wrote: > Gleb Natapov wrote: >> On Thu, Aug 27, 2009 at 09:40:06AM +0200, Gerd Hoffmann wrote: >>> Or does it mean we must emulate a more recent chipset? >>> >> That too will work. > > > Note that if you change the chipset, it'll break some existing Windows VMs. I think we would rather *add* a new machine type with a new chipset, not *replace* the piix3. IIRC someone is already working on emulation something more recent (ICH9?) to get some modern stuff, so that will probably get us some more ioapic lines. > I had this problem when porting a Windows Server 2003 VM from Virtual > PC to QEMU: Virtual PC emulates a PIIX4, while QEMU provides a PIIX3 > (even though there's a PIIX4 in the source code, it's not used for PC > emulation). The ported image would not boot because of the change of > chipset, until I patched the registry to accomodate the change. Any hints where do dig in the registy? I have a dead notebook with xp (disk still ok), trying to boot the disk image in kvm, and of course it doesn't work due to the hardware being different. Googleing the STOP code printed on the blue screen hinted that xp fails to access the hard drive ... It is a 5-year old intel laptop, so it probably is something like moving from ICH6 to PIIX3 ... thanks, Gerd