qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Sebastian Herbszt" <herbszt@gmx.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] APM regression since v1.3.0-408-g9ee59f3
Date: Wed, 24 Jul 2013 20:38:07 +0200	[thread overview]
Message-ID: <B8B1BBBE58C44CCDBB774DA78BF30CE1@FSCPC> (raw)
In-Reply-To: <51EE778A.5030905@redhat.com>

Gerd Hoffmann wrote:
> On 07/03/13 22:25, Sebastian Herbszt wrote:
>> Commit 9ee59f3 ("pc: remove bochs bios debug ports") broke the APM
>> interface
>> between QEMU and Bochs BIOS/SeaBIOS. Without APM support older guests
>> are no longer able to power off the VM. This regression also affects
>> older machine
>> types like pc-1.2.
> 
> --verbose please.  Which guest?  Which firmware?

The guest is syslinux. Its poweroff module [1] uses the APM interface.
I'am also no longer able to power off linux (2.6.20) with acpi=off.

Firmware is SeaBIOS 1.7.2.

> ACPI poweroff with seabios works just fine.  If APM support in seabios
> uses something else it should be switched to use the same hardware ports
> ACPI uses for poweroff (some piix4 pm device register I think) instead
> of the debug ports which where never meant to be used that way.

SeaBIOS uses the same QEMU / BIOS interface as Bochs BIOS (port 0x8900).
This interface was removed by commit 9ee59f3.

> Does bochs bios run on recent qemu versions in the first place?

Last time I checked it did, but "recent" is relative.

[1] http://www.syslinux.org/archives/2013-July/020367.html

Sebastian

      reply	other threads:[~2013-07-24 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 20:25 [Qemu-devel] APM regression since v1.3.0-408-g9ee59f3 Sebastian Herbszt
2013-07-23 12:31 ` Gerd Hoffmann
2013-07-24 18:38   ` Sebastian Herbszt [this message]

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=B8B1BBBE58C44CCDBB774DA78BF30CE1@FSCPC \
    --to=herbszt@gmx.de \
    --cc=aliguori@us.ibm.com \
    --cc=kraxel@redhat.com \
    --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).