From: Graeme Brett Houston BSc <1874504@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1874504] [NEW] VFIO passthrough spits out thousands of messages
Date: Thu, 23 Apr 2020 17:49:32 -0000 [thread overview]
Message-ID: <158766417277.8728.12362820918014730192.malonedeb@gac.canonical.com> (raw)
Public bug reported:
started qemu as:
sudo qemu-system-sparc64 -device vfio-pci,host=0b:05.0,x-no-mmap=on,bus=pciB
messages received thousands of times:
qemu-system-sparc64: -device vfio-pci,host=0b:05.0,x-no-mmap=on,bus=pciB: iommu has granularity incompatible with target AS
qemu-system-sparc64: -device vfio-pci,host=0b:05.0,x-no-mmap=on,bus=pciB: iommu map to non memory area 4079c000
qemu version (think telling a lie as sure its 5.0)
QEMU emulator version 4.2.92
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
pci device being passed through:
0b:05.0 Display controller [0380]: 3DLabs Permedia II 2D+3D [3d3d:0009] (rev 01)
Subsystem: Tech-Source Permedia II 2D+3D [1227:0006]
Flags: medium devsel, IRQ 11
Memory at 83000000 (32-bit, non-prefetchable) [disabled] [size=128K]
Memory at 82800000 (32-bit, non-prefetchable) [disabled] [size=8M]
Memory at 82000000 (32-bit, non-prefetchable) [disabled] [size=8M]
Expansion ROM at 83020000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: vfio-pci
** Affects: qemu
Importance: Undecided
Status: New
** Tags: sparc64 vfio
** Attachment added: "output.txt"
https://bugs.launchpad.net/bugs/1874504/+attachment/5358566/+files/output.txt
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1874504
Title:
VFIO passthrough spits out thousands of messages
Status in QEMU:
New
Bug description:
started qemu as:
sudo qemu-system-sparc64 -device vfio-pci,host=0b:05.0,x-no-mmap=on,bus=pciB
messages received thousands of times:
qemu-system-sparc64: -device vfio-pci,host=0b:05.0,x-no-mmap=on,bus=pciB: iommu has granularity incompatible with target AS
qemu-system-sparc64: -device vfio-pci,host=0b:05.0,x-no-mmap=on,bus=pciB: iommu map to non memory area 4079c000
qemu version (think telling a lie as sure its 5.0)
QEMU emulator version 4.2.92
Copyright (c) 2003-2020 Fabrice Bellard and the QEMU Project developers
pci device being passed through:
0b:05.0 Display controller [0380]: 3DLabs Permedia II 2D+3D [3d3d:0009] (rev 01)
Subsystem: Tech-Source Permedia II 2D+3D [1227:0006]
Flags: medium devsel, IRQ 11
Memory at 83000000 (32-bit, non-prefetchable) [disabled] [size=128K]
Memory at 82800000 (32-bit, non-prefetchable) [disabled] [size=8M]
Memory at 82000000 (32-bit, non-prefetchable) [disabled] [size=8M]
Expansion ROM at 83020000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: vfio-pci
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1874504/+subscriptions
next reply other threads:[~2020-04-23 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 17:49 Graeme Brett Houston BSc [this message]
2020-10-17 17:51 ` [Bug 1874504] Re: VFIO passthrough spits out thousands of messages Artyom Tarasenko
2021-05-06 13:37 ` Thomas Huth
2021-07-06 4:17 ` Launchpad Bug Tracker
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=158766417277.8728.12362820918014730192.malonedeb@gac.canonical.com \
--to=1874504@bugs.launchpad.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).