Re: APM bug Re: [Qemu-devel] Re: Suggestion - trap window-close of VM

[Jason Gress <jasong@ccgr.org>]

On Thursday 31 March 2005 10:38 am, Andreas Bollhalder wrote:
> My Windows XP guests are also unable to power off QEMU. As I know,
> there is the posibillity to install W2K or XP without ACPI support.
> Has anyone tried that ? Could it be, that the default installation of
> Windows with ACPI disable the APM support ? My brain is remembering
> something... Win98 guest closes QEMU fine.
>
> Andreas

Win2k/XP can be told to setup w/o ACPI by pressing F5 during the install 
sequence, right around when it asks for F6 for additional SCSI drivers.  If I 
remember correctly, on normal hardware that prevents the system from turning 
off automatically even when a similar Win98 might do that.  You could give it 
a try, but I'd be surprised if that worked.

 Jason

>
> > -----Original Message-----
> > From: qemu-devel-bounces+bolle=geodb.org@nongnu.org
> > [mailto:qemu-devel-bounces+bolle=geodb.org@nongnu.org] On
> > Behalf Of Struan Bartlett
> > Sent: Wednesday, March 30, 2005 3:22 PM
> > To: qemu-devel@nongnu.org
> > Subject: APM bug Re: [Qemu-devel] Re: Suggestion - trap
> > window-close of VM
> >
> >
> > *This message was transferred with a trial version of
> > CommuniGate(tm) Pro*
> >
> > Paul Brook wrote:
> > >>This isn't working quite right for me with a Windows 98 guest --
>
> it
>
> > >>traps the attempt to close the window all right, but it doesn't
>
> let
>
> > >>the window close even when Window 98 has in fact shut down.
> > >
> > >In theory windows should be able to "turn off" qemu using
> >
> > APM, like it does on
> >
> > >real machines. However there seem to be bugs in the qemu
> >
> > implementation that
> >
> > >stop this working.
> >
> > I thought I'd have a little look into why Windows 2000
> > doesn't turn off
> > qemu using APM properly. I enabled DEBUG_BIOS in hw/pc.c then
> > downloaded
> > the latest Debian source for the Bochs bios v1.121 and defined
> > DEBUG_ROMBIOS and DEBUG_APM both to be 1. I recompiled and
> > installed the
> > bios and ran qemu to load up Windows 2000. What we get seems
> > interesting. By the time Qemu boots Windows 2000 to its first
> > progress-bar, it has printed the following debug statements (with my
> >
> > explanation added in square brackets):
> >
> > APM: EAX=00005300 [53 is the int 15h identifier for APM
> > checked for in
> > rombios.c. 00 is the APM installation check function]
> > APM: EAX=00005301 [01 is the APM real mode interface connect]
> > APM: EAX=0000530e [0e appears to request APM driver version]
> > APM: EAX=00005300 [00, again, is the APM installation check - why is
> >
> > this called twice?]
> > APM: EAX=00005304 [04 is APM interface disconnect]
> >
> > Then, while Windows 2000 boots and until shutdown is
> > complete, I get no
> > more debug statements. My question is, why not? I'm no APM
> > expert but,
> > judging from the 'apmbios.S' comments I might expect to see APM:
> > EAX=00005303 [03 is APM 32 bit protected mode interface connect]. I
> > could speculate that the return code from APM function 0e does not
> > satisfy Windows 2000 for some reason, so it does another
>
> installation
>
> > check and then disconnects the APM interface entirely - hence no APM
> >
> > functionality in Windows 2000.
> >
> > If I get more time I may research the APM functions more
> > fully. In the
> > meantime, if anyone can suggest any alternative theories or
> > how to test
> > them, I'd be curious.
> >
> > Struan
> >
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel