qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] Add option to disable FDC from ISA bus and ACPI


From: Gabriel L. Somlo
Subject: Re: [Qemu-devel] [PATCH] Add option to disable FDC from ISA bus and ACPI on i386
Date: Thu, 9 Jan 2014 13:51:46 -0500
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Jan 09, 2014 at 03:51:17AM +0200, Michael S. Tsirkin wrote:
> I was hoping we can figure out a configuration that makes
> os x work without hurting xp *and* without just rudely
> detecting os x through the SMC._STA hack.

Sadly, uncommenting "IRQNoFlags() {2, 8}" in HPET._CRS still causes XP
to bluescreen.

I've seen IRQNoFlags included with HPET._CRS on plenty instances of real
hardware, so this must be some sort of second-order effect.

The exact message on the XP bluescreen is:

    The BIOS in this system is not fully ACPI compliant. Please
    contact your system vendor or visit http://www.hardware-update.com
    for an updated BIOS. If you are unable to obtain an updated BIOS
    or the latest BIOS supplied by your vendor is not ACPI compliant,
    you can turn off ACPI mode during text mode setup. To do this,
    simply press the F7 key when you are prompted to install storage
    drivers. The system will not notify you that the F7 was
    pressed - it will silently disable ACPI and allow you to continue
    your installation.

    Technical information:

    *** STOP: 0x000000A5 (0x00010006,0x89A5D880,0x00000000,0x00000000)

This while attempting to boot an image installed earlier, on a
released version of QEMU, presumably with "functioning" ACPI.

When booting from the XP-SP2 DVD, the bluescreen message read
slightly different:

    Check to be sure you have adequate disk space. If a driver is
    identified in the Stop message, disable the driver or check with the
    manufacturer for driver updates. Try changing video adapters.

    Check with your hardware vendor for any BIOS updates. Disable BIOS
    memory options such as caching or shadowing. If you need to use Safe
    Mode to remove or disable components, restart your computer, press F8
    to select Advanced Startup Options, and then select Safe Mode.

    Technical information:

    *** STOP: 0x0000007e (0xC0000005,0xF73B8D66,0xF78D1EA0,0xF78D1B9C)

    ***      acpi.sys - Address F73B8D66 base at F73AD000, DateStamp 41107d27

But, following the tip in the *first* message (hitting F7 during
install) gets me a working (if de-ACPI-fied) XP install.

I don't know if/how to de-ACPI-fy an already installed XP disk image,
but even if I did, that still feels "wrong".

All this on piix (after uncommenting IRQNoFlags in HPET._CRS).


With current/unchanged HPET._CRS, OS X boots fine (SnowLeopard only so
far) on q35 in both smp and up mode, and -- I just figured this out --
on piix up only.

When I try to boot SnowLeopard in smp on piix, I get an xnu hpet
panic:

    panic(cpu 2 caller 0xffffff7f80864f8b): "No HPETs available...CPU(s)
    configured
    incorrectly\n"@/SourceCache/AppleIntelCPUPowerManagement/
    AppleIntelCPUPowerManagement-142.6/pmThread.c:157
    Debugger called:<panic>


Whatever we do, we're not lying about ACPI convincingly enough, to
either XP or OS X :) I'm relatively new to ACPI, so any other ideas
on where to focus would be much appreciated !

Thanks,
--Gabriel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]