From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip
Date: Wed, 2 Feb 2011 15:18:48 +0200 [thread overview]
Message-ID: <20110202131848.GH14984@redhat.com> (raw)
In-Reply-To: <4D4958B2.4070709@redhat.com>
On Wed, Feb 02, 2011 at 03:14:26PM +0200, Avi Kivity wrote:
> On 02/02/2011 03:11 PM, Gleb Natapov wrote:
> >On Wed, Feb 02, 2011 at 02:09:24PM +0100, Jan Kiszka wrote:
> >> On 2011-02-02 14:05, Avi Kivity wrote:
> >> > On 02/02/2011 02:50 PM, Jan Kiszka wrote:
> >> >>>>
> >> >>> Opps, -smp 1. With -smp 2 it boot almost completely and then hangs.
> >> >>
> >> >> Ah, good (or not good). With Windows 2003 Server, I actually get a Blue
> >> >> Screen (Stop 0x000000b8).
> >> >
> >> > Userspace APIC is broken since it may run with an outdated cr8, does
> >> > reverting 27a4f7976d5 help?
> >> >
> >>
> >> -ECOMMITNOTFOUND, neither in qemu-kvm nor upstream.
> >>
> >This is kernel commit, but it is too old. I am pretty sure userspace irq
> >chip worked back then.
>
> I have memories of it failing autotest, but the conclusion was that
> the commit did not cause the problem, simply enlarged the window in
> which it could happen.
>
Ah, I remember something like that. RHEL6 kernel + qemu-kvm fails
in the same way so problem is not new.
--
Gleb.
next prev parent reply other threads:[~2011-02-02 14:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 18:02 [Qemu-devel] KVM: Windows 64-bit troubles with user space irqchip Jan Kiszka
2011-02-02 11:55 ` Gleb Natapov
2011-02-02 11:58 ` Jan Kiszka
2011-02-02 12:35 ` Gleb Natapov
2011-02-02 12:50 ` Jan Kiszka
2011-02-02 13:05 ` Avi Kivity
2011-02-02 13:09 ` Jan Kiszka
2011-02-02 13:11 ` Gleb Natapov
2011-02-02 13:14 ` Avi Kivity
2011-02-02 13:18 ` Gleb Natapov [this message]
2011-02-02 14:30 ` Jan Kiszka
2011-02-02 14:35 ` Avi Kivity
2011-02-02 14:43 ` Jan Kiszka
2011-02-02 14:52 ` Jan Kiszka
2011-02-02 15:09 ` Avi Kivity
2011-02-02 15:35 ` Jan Kiszka
2011-02-02 15:44 ` Avi Kivity
2011-02-02 15:46 ` Gleb Natapov
2011-02-02 15:52 ` Jan Kiszka
2011-02-02 16:29 ` Gleb Natapov
2011-02-02 16:36 ` Jan Kiszka
2011-02-02 16:39 ` Gleb Natapov
2011-02-02 16:51 ` Jan Kiszka
2011-02-03 7:42 ` Gleb Natapov
2011-02-03 9:31 ` Jan Kiszka
2011-02-03 8:18 ` Avi Kivity
2011-02-03 9:32 ` Jan Kiszka
2011-02-03 10:01 ` Avi Kivity
2011-02-03 10:14 ` Jan Kiszka
2011-02-03 10:04 ` Marcelo Tosatti
2011-02-03 10:11 ` Jan Kiszka
2011-02-03 14:15 ` Gleb Natapov
2011-02-03 14:27 ` Jan Kiszka
2011-02-06 10:26 ` Avi Kivity
2011-02-06 10:28 ` Gleb Natapov
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=20110202131848.GH14984@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--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).