From: Gerd Hoffmann <kraxel@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>,
Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] Route IOAPIC interrupts via ISA bus
Date: Thu, 27 Aug 2009 10:55:54 +0200 [thread overview]
Message-ID: <4A964A1A.90604@redhat.com> (raw)
In-Reply-To: <20090827081832.GA22631@shareable.org>
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
next prev parent reply other threads:[~2009-08-27 8:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-09 16:44 [Qemu-devel] [PATCH 0/2] Disentagle ISA IRQs Avi Kivity
2009-08-09 16:44 ` [Qemu-devel] [PATCH 1/2] Route PC irqs to ISA bus instead of i8259 directly Avi Kivity
2009-08-10 8:34 ` Gerd Hoffmann
2009-08-10 8:46 ` Avi Kivity
2009-08-10 9:04 ` Alexander Graf
2009-08-10 9:43 ` Avi Kivity
2009-08-10 9:45 ` Stefan Assmann
2009-08-10 9:52 ` Avi Kivity
2009-08-10 13:20 ` Olaf Dabrunz
2009-08-10 13:14 ` Olaf Dabrunz
2009-08-09 16:44 ` [Qemu-devel] [PATCH 2/2] Route IOAPIC interrupts via ISA bus Avi Kivity
2009-08-10 8:38 ` Gerd Hoffmann
2009-08-26 16:03 ` Gerd Hoffmann
2009-08-26 16:06 ` Avi Kivity
2009-08-26 16:30 ` Gerd Hoffmann
2009-08-26 19:09 ` Gleb Natapov
2009-08-27 7:40 ` Gerd Hoffmann
2009-08-27 7:57 ` Gleb Natapov
2009-08-27 8:18 ` Jamie Lokier
2009-08-27 8:24 ` Gleb Natapov
2009-08-27 8:55 ` Gerd Hoffmann [this message]
2009-08-27 10:35 ` Isaku Yamahata
2009-08-27 21:07 ` [Qemu-devel] " Bjørn Mork
2009-08-27 4:53 ` [Qemu-devel] " Avi Kivity
2009-08-27 7:35 ` Gerd Hoffmann
2009-08-27 7:57 ` Avi Kivity
2009-08-27 8:13 ` Gerd Hoffmann
2009-08-27 8:26 ` Avi Kivity
2009-08-28 2:20 ` Beth Kon
2009-08-29 17:47 ` Avi Kivity
2009-08-30 2:09 ` Beth Kon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A964A1A.90604@redhat.com \
--to=kraxel@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jamie@shareable.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).