From: Alex Williamson <alex.williamson@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: "Shlomo Pongratz" <shlomopongratz@gmail.com>,
"Cédric Le Goater" <clg@redhat.com>,
qemu-discuss <qemu-discuss@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Eric Auger" <eric.auger@redhat.com>
Subject: Re: Usage of vfio-pci without KVM.
Date: Tue, 12 Sep 2023 06:57:53 -0600 [thread overview]
Message-ID: <20230912065753.37de2393.alex.williamson@redhat.com> (raw)
In-Reply-To: <be58faf9-8218-e085-7dc3-b9c2858adac8@linaro.org>
On Tue, 12 Sep 2023 14:47:41 +0200
Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
> Cc'ing VFIO maintainers.
>
> On 12/9/23 14:39, Shlomo Pongratz wrote:
> > Hi,
> > I'm running qemu-system-aarch64 (QEMU emulator version 7.0.93) on
> > Ubuntu 20.04.4 LTS i with Intel's i7.
> > I'm trying to pass a Samsung NVME device using vfio-pci. I detached
> > the device from the nvme driver and attached it to the vfio-pci.
> > Using lspci I can see "Kernel driver in use: vfio-pci"
> > In QEMU script I've written "-device vfio-pci,host=0000:03:00.0" where
> > 0000:03:00.0 is the device PCI address.
> > I get the error
> > qemu-system-aarch64: -device vfio-pci,host=0000:03:00.0: VFIO_MAP_DMA
> > failed: Invalid argument
> > qemu-system-aarch64: -device vfio-pci,host=0000:03:00.0: vfio
> > 0000:03:00.0: failed to setup container for group 15: memory listener
> > initialization failed: Region mach-virt.ram:
> > vfio_dma_map(0x55855c75bf00, 0x40000000, 0x100000000, 0x7f5197e00000)
> > = -22 (Invalid argument
> >
> > My question is vfio-pci is supported with cross architecture?
It does, but reserved address ranges need to be honored. x86 has a
reserved range at 0xfee00000 for MSI mapping, so the VM address space
needs to be such that it avoids trying to place mappings there. Thanks,
Alex
next prev parent reply other threads:[~2023-09-12 12:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHzK-V2a-tW8BQBJNurf0QogTNYH3_oEg7HAfi-dSU_3D626Tw@mail.gmail.com>
2023-09-12 12:47 ` Usage of vfio-pci without KVM Philippe Mathieu-Daudé
2023-09-12 12:57 ` Alex Williamson [this message]
2023-09-12 13:22 ` Shlomo Pongratz
2023-09-12 13:56 ` Alex Williamson
2023-09-15 12:01 ` Cédric Le Goater
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=20230912065753.37de2393.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=eric.auger@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=shlomopongratz@gmail.com \
/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).