kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: "Kevin O'Connor" <kevin@koconnor.net>,
	Ruben Kerkhof <ruben@rubenkerkhof.com>,
	Teck Choon Giam <giamteckchoon@gmail.com>,
	kvm@vger.kernel.org, seabios@seabios.org
Subject: Re: system_powerdown not working for qemu-kvm 0.12.4?
Date: Tue, 12 Oct 2010 09:25:59 +0200	[thread overview]
Message-ID: <4CB40D87.6000405@redhat.com> (raw)
In-Reply-To: <20101012071404.GA18974@redhat.com>

  On 10/12/2010 09:14 AM, Gleb Natapov wrote:
> On Tue, Oct 12, 2010 at 03:11:24AM -0400, Kevin O'Connor wrote:
> >  On Tue, Oct 12, 2010 at 08:49:58AM +0200, Avi Kivity wrote:
> >  >   On 10/11/2010 07:53 PM, Ruben Kerkhof wrote:
> >  >  >5c99b6c984682ddb1d4543a7e27a1f4ca633e6a6 is the first bad commit
> >  >  >commit 5c99b6c984682ddb1d4543a7e27a1f4ca633e6a6
> >  >  >Author: Kevin O'Connor<kevin@koconnor.net>
> >  >  Gleb, Kevin, any ideas?
> >  >
> >  >  (summary: qemu-kvm doesn't acpi shutdown freebsd 8.1 with this
> >  >  commit; qemu.git does.  May be due to interrupt polarity which kvm
> >  >  implements but qemu does not)
> >
> >  The only thing in commit 5c99b6c9 that could cause an issue is that it
> >  has the compiled acpi changes actually made in commit 29f4b912, but I
> >  don't see how that would be a problem to reboots:
> >
> It makes line 0 of device 1 to be active low instead of active high.

Correctly, according to the documentation (the line is marked IRQ9OUT#, 
which indicates it's active low, though that isn't set down elsewhere).

Qemu however emulates it as active high.  Other guests work, which is wierd.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2010-10-12  7:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-15  1:19 system_powerdown not working for qemu-kvm 0.12.4? Teck Choon Giam
2010-05-15  9:36 ` Michael Tokarev
2010-05-16 11:52 ` Avi Kivity
2010-05-19  9:23   ` Teck Choon Giam
2010-05-19 16:22     ` Avi Kivity
2010-08-14 23:32       ` Teck Choon Giam
2010-08-15 11:00         ` Avi Kivity
2010-08-15 16:15           ` Teck Choon Giam
2010-08-15 16:19             ` Avi Kivity
2010-08-15 17:53               ` Teck Choon Giam
2010-10-07 12:30                 ` Teck Choon Giam
2010-10-11 16:29           ` Ruben Kerkhof
2010-10-11 16:57             ` Avi Kivity
2010-10-11 17:53               ` Ruben Kerkhof
2010-10-12  6:49                 ` Avi Kivity
2010-10-12  7:11                   ` Kevin O'Connor
2010-10-12  7:14                     ` Gleb Natapov
2010-10-12  7:25                       ` Avi Kivity [this message]
2010-10-12  7:33                         ` Avi Kivity
2010-10-12  7:39                           ` Avi Kivity
2010-10-12  7:40                           ` Gleb Natapov
2010-10-12  7:44                             ` Avi Kivity
2010-10-15  1:45                     ` Ruben Kerkhof
2010-10-15  7:01                       ` Gleb Natapov
2010-10-15 14:26                         ` Ruben Kerkhof
2010-10-15 15:53                           ` Teck Choon Giam

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=4CB40D87.6000405@redhat.com \
    --to=avi@redhat.com \
    --cc=giamteckchoon@gmail.com \
    --cc=gleb@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kvm@vger.kernel.org \
    --cc=ruben@rubenkerkhof.com \
    --cc=seabios@seabios.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).