qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Guenter Roeck <linux@roeck-us.net>,
	Keith Busch <kbusch@kernel.org>, Klaus Jensen <its@irrelevant.dk>
Cc: Kevin Wolf <kwolf@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Dropped/disabled NVME support in qemu
Date: Mon, 21 Dec 2020 15:11:02 +0100	[thread overview]
Message-ID: <77d714a6-9922-1541-9f32-6ccb6ff9ea0f@redhat.com> (raw)
In-Reply-To: <bcf1a98d-e86b-7b34-e384-b4b7e0e22747@roeck-us.net>

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
> 



  reply	other threads:[~2020-12-21 14:12 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é [this message]
2020-12-21 15:17   ` Klaus Jensen
2020-12-21 15:55     ` Guenter Roeck

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=77d714a6-9922-1541-9f32-6ccb6ff9ea0f@redhat.com \
    --to=philmd@redhat.com \
    --cc=its@irrelevant.dk \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=linux@roeck-us.net \
    --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).