From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Unknown PCI Bridge
Date: Thu, 04 May 2006 22:01:05 -0500 [thread overview]
Message-ID: <pan.2006.05.05.03.01.05.359847@codemonkey.ws> (raw)
In-Reply-To: 445A4520.9040300@bellard.org
On Thu, 04 May 2006 20:17:04 +0200, Fabrice Bellard wrote:
> Chris Bagwell wrote:
>> Hi all,
>>
>> I upgraded to current CVS (0.8.1 plus a couple of patches like acpi).
>> Last time I upgraded was about 1 week ago.
>>
>> When I ran this version with a win98 guest, windows detected a new
>> device called "PCI Bridge". It was unable to find a driver for this on
>> the win98 CD and placed it as not working in the "other devices" section
>> of device manager.
>>
>> Doesn't seem to harm anything. I was guessing it had something to do
>> with the acpi patches but haven't verified. Any ideas?
>
> Yes, ACPI adds a new PCI device so it is normal. I am interested by any
> regression found using the current CVS with ACPI...
Win2k and Linux 2.6 (w/o kqemu) seem to work fine.
with -kernel-kqemu and 2.6.15, I get:
Uncompressing Linux... Ok, booting the kernel.
BIOS bug, local APIC #0 not detected!
IOAPIC[0]: Invalid reference to IRQ 0
IOAPIC[0]: Invalid reference to IRQ 0
PCI PIIX3: Enabling Passive Release on 0000:00:01.0
ALERT! /dev/hda1 does not exist. Dropping to a shell!
Regards,
Anthony Liguori
> Fabrice.
next prev parent reply other threads:[~2006-05-05 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-04 13:41 [Qemu-devel] Unknown PCI Bridge Chris Bagwell
2006-05-04 18:17 ` Fabrice Bellard
2006-05-05 0:39 ` [Qemu-devel] " Sven Köhler
2006-05-05 12:28 ` malc
2006-05-05 15:45 ` Sven Köhler
2006-05-05 16:34 ` malc
2006-05-05 17:32 ` Sven Köhler
2006-05-05 17:52 ` malc
2006-05-05 3:01 ` Anthony Liguori [this message]
2006-05-06 20:52 ` Sven Köhler
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=pan.2006.05.05.03.01.05.359847@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).