From: Hannes Reinecke <hare@suse.de>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Alexander Graf <agraf@suse.de>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] Windows doesn't like MSI/MSI-X
Date: Thu, 07 Mar 2013 15:48:05 +0100 [thread overview]
Message-ID: <5138A8A5.1020706@suse.de> (raw)
Hi all,
recently I've tried to teach megasas MSI/MSI-X. While it works
perfectly under Linux, Windows refuses to.
With really strange symptoms:
Windows Vista will BSOD when both MSI/MSI-X registers are present,
and Windows 7 will hang as Windows (apparently) thinks MSI/MSI-X is
enabled, whereas qemu doesn't and uses INTx.
So the Windows 7 guest will never see any interrupts.
The _really_ odd thing is that when I remove the MSI-X capability
Windows will fall back to INTx and everything works.
Even more curious is that from the logs Windows will only ever write
zeros into the MSI/MSI-X config registers.
Which makes me wonder what's going on there.
As I'm not sure if that's my fault I was wondering if anybody every
succeeded in getting AHCI to use MSI under Windows.
Any pointers?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
reply other threads:[~2013-03-07 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5138A8A5.1020706@suse.de \
--to=hare@suse.de \
--cc=agraf@suse.de \
--cc=mst@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).