From: Guenter Roeck <linux@roeck-us.net>
To: "Klaus Jensen" <its@irrelevant.dk>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Keith Busch <kbusch@kernel.org>, Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Dropped/disabled NVME support in qemu
Date: Mon, 21 Dec 2020 07:55:41 -0800 [thread overview]
Message-ID: <a9c08af4-50b8-a8f7-b6c2-31cc3a3974e1@roeck-us.net> (raw)
In-Reply-To: <X+C8dpngmpVsy0Q3@apples.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 1907 bytes --]
Hi Klaus,
On 12/21/20 7:17 AM, Klaus Jensen wrote:
> On Dec 21 15:11, Philippe Mathieu-Daudé wrote:
>> Cc'ing NVMe emulation maintainers.
>>
>> On 12/21/20 6:12 AM, Guenter Roeck wrote:
>>> Hi all,
>>>
>>> since qemu v5.1, nvme support has been dropped from several architectures.
>>> Well, it was not exactly dropped, but disabled.
>>>
>>> On those architectures, trying to boot from an nvme drive now results
>>> in the following or a similar error message.
>>>
>>> qemu-system-alpha: -device nvme,serial=foo,drive=d0: MSI-X is not supported by interrupt controller
>>>
>>> This is the result of the following two commits.
>>>
>>> fbf2e5375e ("hw/block/nvme: Verify msix_vector_use() returned value")
>>> 1c0c2163aa ("hw/block/nvme: verify msix_init_exclusive_bar() return value")
>>>
>>> Affected architectures are alpha, parisc, ppc, sh, and sparc, and every other
>>> architecture/platform where the interrupt controller does not support MSI-X.
>>> After reverting above patches, I can boot from nvme again.
>>>
>>> This does not really matter for me - I run my own versions of qemu anyway,
>>> and don't mind carrying reverts if I have to. However, for my education,
>>> I would like to understand why nvme support was disabled, especially since
>>> it seemed to work for me just fine for years. Can someone please explain ?
>>>
>>> Thanks,
>>> Guenter
>>>
>>
>
> Hi Guenter,
>
> Thanks for reporting this. My apologies - this is an unintended
> regression. I'll get a revert staged.
>
> I'll of course also look into why this was not picked up doing testing.
> There is an nvme QTest that should have picked this up, but it obviously
> was not run for these architectures.
>
Ah, that explains a lot. Just a thought: instead of reverting the patches,
it might possibly make sense to handle lack of MSI-X support explicitly.
Thanks,
Guenter
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-12-21 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-21 5:12 Dropped/disabled NVME support in qemu Guenter Roeck
2020-12-21 14:11 ` Philippe Mathieu-Daudé
2020-12-21 15:17 ` Klaus Jensen
2020-12-21 15:55 ` Guenter Roeck [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=a9c08af4-50b8-a8f7-b6c2-31cc3a3974e1@roeck-us.net \
--to=linux@roeck-us.net \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=philmd@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).