From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 202055] Failed to PCI passthrough SSD with SMI SM2262 controller.
Date: Wed, 29 Jul 2020 14:34:36 +0000 [thread overview]
Message-ID: <bug-202055-28872-Pg0fhycQNR@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202055-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202055
--- Comment #47 from FCL (Felix.leclair123@hotmail.com) ---
(In reply to FCL from comment #46)
> Hey gents!
>
> Trying to apply this to a proxmox VM, any advice on how to do so? I'm
> running on top of the 5.4.x linux kernel. I'm experiencing the same bug as
> in topic name, using the SMI 2263 controller. (Adata as above)
>
> Anything I can provide in terms of debugging data? Otherwise, any advice on
> how to use the above non kernel patch? also comfortable doing a kernel
> recompile if thats the better solution. Will be going to a FreeBSD (FreeNAS
> 11.3) VM with 4 threads and 72GB of ram alongside an LSI SAS controller.
>
> Platform is a Dual Xeon 5670 on a HP ml350 G6 mother board.
>
> Also attached but on a different VM is a Radeon 5600XT, an intel USB
> controller and an intel Nic to a windows VM
Found the solution without the need for a kernel recompile. in my Qemu conf
file added:
args: -set device.hostpci1.x-msix-relocation=bar2
Where hostpci1 is
hostpci1: 08:00.0
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-07-29 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-202055-28872@https.bugzilla.kernel.org/>
2019-04-08 4:16 ` [Bug 202055] Failed to PCI passthrough SSD with SMI SM2262 controller bugzilla-daemon
2019-04-09 14:43 ` bugzilla-daemon
2019-04-09 14:57 ` bugzilla-daemon
2020-07-28 15:41 ` bugzilla-daemon
2020-07-29 14:34 ` bugzilla-daemon [this message]
2020-12-29 1:00 ` bugzilla-daemon
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=bug-202055-28872-Pg0fhycQNR@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.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).