From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
"Michael S. Tsirkin" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
KVM list <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15
Date: Tue, 06 Dec 2011 20:57:46 +0400 [thread overview]
Message-ID: <4EDE498A.2040309@msgid.tls.msk.ru> (raw)
In-Reply-To: <4EDE450B.6090801@siemens.com>
On 06.12.2011 20:38, Jan Kiszka wrote:
> On 2011-12-06 17:29, Michael Tokarev wrote:
[]
>> It appears there are two issues here, one is fixed by
>> 09de0f469c3c2a277c7874f6c60992c8b94719a9 and is 32bit-only, and
>> another bisect leads to this commit:
Or 3... :)
>> commit 59539c913383fdd3350681301b44f02fa7ee2757
>> Author: Jan Kiszka <jan.kiszka@siemens.com>
>> Date: Mon Jun 27 12:22:28 2011 +0200
>>
>> qemu-kvm: Fix in-kernel PIC reset
[]
>> Anything wrong with this patch?
>
> I tend to say "no". It may just reveals some issue elsewhere.
>
> To cross-check: Does this series [1] expose the same issue with vanilla
> QEMU when enabling that in-kernel irqchip version?
I cross-checked it the other way, which really should have been done
at the very beginning instead of wasting so much time of so many
people at once. I just tried qemu-kvm-1.0, which I wasn't due to
an unrelated issue (1.0 does not work for me in my funky 32/64bit
environment). Also, since the bug has been reported especially
against 0.15 version (triggering by upgrading from 0.14 to 0.15),
I didn't insist on trying 1.0, which was my biggest mistake.
And in qemu-kvm-1.0, the problem guest Just Works. So i t must be
something else which were fixed between 0.15 and 1.0.
Upstream qemu 1.0 does not have this issue too.
> [1] http://thread.gmane.org/gmane.comp.emulators.kvm.devel/82871
I'll try to verify this series in a moment, but hopefully it will work
fine too :)
Thanks!
/mjt
next prev parent reply other threads:[~2011-12-06 16:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EDC8D06.20308@msgid.tls.msk.ru>
[not found] ` <4EDCC6FE.8040702@redhat.com>
[not found] ` <4EDD2763.8010808@msgid.tls.msk.ru>
[not found] ` <4EDDEF26.9030403@redhat.com>
[not found] ` <4EDDF659.6040701@msgid.tls.msk.ru>
2011-12-06 12:27 ` [Qemu-devel] winXP "Standard PC" HAL and qemu-kvm >= 0.15 Michael S. Tsirkin
2011-12-06 14:45 ` Michael Tokarev
2011-12-06 16:29 ` Michael Tokarev
2011-12-06 16:38 ` Jan Kiszka
2011-12-06 16:57 ` Michael Tokarev [this message]
2011-12-06 17:45 ` Jan Kiszka
2011-12-06 18:13 ` Michael Tokarev
2011-12-06 18:21 ` Jan Kiszka
2011-12-06 18:45 ` Michael Tokarev
2011-12-06 19:38 ` Michael Tokarev
2011-12-06 20:58 ` Jan Kiszka
2011-12-06 21:12 ` Jan Kiszka
2011-12-07 7:11 ` Michael Tokarev
2011-12-07 9:02 ` Kevin Wolf
2011-12-07 9:31 ` Michael Tokarev
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=4EDE498A.2040309@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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).