zinkpro45 Posted January 8, 2019 Share Posted January 8, 2019 3 hours ago, limetech said: We can try to add that patch to upcoming Unraid 6.7 release which is on 4.19 kernel at the moment. That would be amazing, thanks! Quote Link to comment
gleech Posted January 23, 2019 Share Posted January 23, 2019 Can some confirm with a working vm. I think this is already fix on the new 6.7 RC1 version. I have a vm setup but its not showing any video yet, I have to play with the video setting. But I'm not getting any error anymore if I passthrough my Adata SX8200. Quote Link to comment
limetech Posted January 23, 2019 Share Posted January 23, 2019 2 hours ago, gleech said: Can some confirm with a working vm. I think this is already fix on the new 6.7 RC1 version. Correct. Patch referenced earlier by @aw_ earlier in the topic has been applied to kernel used in 6.7.0-rc1. Please confirm if this solves the issue. Quote Link to comment
Initial.F Posted January 23, 2019 Share Posted January 23, 2019 The problem also seems to occur with NVMe's using the Silicon Motion SM2263 controller. In my case the Crucial P1 (CT500P1SSD8). I'm running version 6.7.0-rc1 and get the same error:internal error: qemu unexpectedly closed the monitor: 2019-01-23T17:55:09.769688Z qemu-system-x86_64: -device vfio-pci,host=82:00.0,id=hostdev0,bus=pci.4,addr=0x0: vfio 0000:82:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align Device: [c0a9:2263] 82:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 2263 (rev 03) My Corsair MP510 NVMe with Phison PS5012-E12 controller passes through without any problems. Quote Link to comment
gleech Posted January 23, 2019 Share Posted January 23, 2019 3 hours ago, limetech said: Correct. Patch referenced earlier by @aw_ earlier in the topic has been applied to kernel used in 6.7.0-rc1. Please confirm if this solves the issue. I will report back once I solve my no video issues on my vm. But I think it's fine now since I'm not getting any error anymore on my Adata SX8200 using SM 2262 controller. Quote Link to comment
gleech Posted January 23, 2019 Share Posted January 23, 2019 2 hours ago, Initial.F said: The problem also seems to occur with NVMe's using the Silicon Motion SM2263 controller. In my case the Crucial P1 (CT500P1SSD8). I'm running version 6.7.0-rc1 and get the same error:internal error: qemu unexpectedly closed the monitor: 2019-01-23T17:55:09.769688Z qemu-system-x86_64: -device vfio-pci,host=82:00.0,id=hostdev0,bus=pci.4,addr=0x0: vfio 0000:82:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align Device: [c0a9:2263] 82:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 2263 (rev 03) My Corsair MP510 NVMe with Phison PS5012-E12 controller passes through without any problems. I think the patch that was applied was only for the SM2262 controller. Maybe @aw_ can make another patch for the SM2263 controller. Quote Link to comment
gleech Posted January 24, 2019 Share Posted January 24, 2019 21 hours ago, limetech said: Correct. Patch referenced earlier by @aw_ earlier in the topic has been applied to kernel used in 6.7.0-rc1. Please confirm if this solves the issue. Confirmed. NVMe's with SM2262 controller passing through without problems. Quote Link to comment
limetech Posted January 24, 2019 Share Posted January 24, 2019 Asked Alex over on the kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=202055#c29 Quote Link to comment
limetech Posted January 25, 2019 Share Posted January 25, 2019 On 1/23/2019 at 12:45 PM, gleech said: I think the patch that was applied was only for the SM2262 controller. Maybe @aw_ can make another patch for the SM2263 controller. Please try 6.7.0-rc2. Updated the patch to include the SM2263 controller. Quote Link to comment
Initial.F Posted January 25, 2019 Share Posted January 25, 2019 4 hours ago, limetech said: Please try 6.7.0-rc2. Updated the patch to include the SM2263 controller. Upgraded to 6.7.0-rc2 and I can confirm the patch solved the problem with the Crucial P1 using the SM2263 controller. Passthrough works perfectly now, thank you for the great support! Quote Link to comment
limetech Posted January 25, 2019 Share Posted January 25, 2019 8 hours ago, Initial.F said: Upgraded to 6.7.0-rc2 and I can confirm the patch solved the problem with the Crucial P1 using the SM2263 controller. Passthrough works perfectly now, thank you for the great support! Nice! Thank you for the testing. Unfortunately it appears some manufacturers are 'rebranding' the vendor-id of that chip, so this might end up being an unending series of patches as different products are being used 🤬 Quote Link to comment
xxb Posted February 7, 2019 Share Posted February 7, 2019 (edited) The problem also seems to occur with NVMe's using the Silicon Motion SM2263XT (different from SM2263) controller. In my case the HP EX900 250G. I'm running version 6.7.0-rc2 and get the same error: internal error: qemu unexpectedly closed the monitor: 2019-02-07T17:55:09.769688Z qemu-system-x86_64: -device vfio-pci,host=05:00.0,id=hostdev0,bus=pci.3,addr=0x0: vfio 0000:05:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align IOMMU group 51:[126f:2263] 05:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2263 (rev 03) IOMMU group 52:[126f:2263] 06:00.0 Non-Volatile memory controller: Silicon Motion, Inc. Device 2263 (rev 03) Please add the SM2263XT controller support, Thanks ! Edited February 8, 2019 by xxb Quote Link to comment
urhellishntemre Posted March 2, 2019 Share Posted March 2, 2019 I found another SSD that uses the SM2263 controller, but the patch in 6.7.0-rc5 doesn't work. It's an Intel SSD 660p, internal error: qemu unexpectedly closed the monitor: 2019-03-02T07:23:43.702484Z qemu-system-x86_64: -device vfio-pci,host=08:00.0,id=hostdev2,bus=pci.0,addr=0x8: vfio 0000:08:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align IOMMU group 15:[8086:f1a8] 08:00.0 Non-Volatile memory controller: Intel Corporation Device f1a8 (rev 03) Is there any other information that you may need to get it included? Thanks for all you do @limetech. Quote Link to comment
GameOverPD Posted April 21, 2019 Share Posted April 21, 2019 Got same problem with intel 660p on 6.7.0-rc7. Is there ny news? Quote Link to comment
urhellishntemre Posted April 21, 2019 Share Posted April 21, 2019 I wanted a stable system so I just got a Samsung Evo Plus. Quote Link to comment
limetech Posted April 30, 2019 Share Posted April 30, 2019 This patch has been removed in 6.7.0-rc8 and a different workaround is recommended: https://bugzilla.kernel.org/show_bug.cgi?id=202055#c42 1 Quote Link to comment
cybrnook Posted April 30, 2019 Share Posted April 30, 2019 (edited) 36 minutes ago, limetech said: This patch has been removed in 6.7.0-rc8 and a different workaround is recommended: https://bugzilla.kernel.org/show_bug.cgi?id=202055#c42 Does this mean any VM that has this style nvme passed through to it should limit the allocated cpu cores to 15 or less? Edited April 30, 2019 by cybrnook typos Quote Link to comment
Maker Posted May 4, 2019 Share Posted May 4, 2019 With last workaround Alex recommended on bugzilla I was not able to boot windows (inaccessible boot device) from ssd. Just fyi Quote Link to comment
raidserver Posted May 8, 2019 Share Posted May 8, 2019 (edited) Struggling to passthrough nvme drive too. Crucial CT1000P1SSD8 P1 1 TB [c0a9:2263] 07:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 2263 (rev 03) internal error: qemu unexpectedly closed the monitor: 2019-05-08T16:39:22.718254Z qemu-system-x86_64: -device vfio-pci,host=07:00.0,id=hostdev3,bus=pci.0,addr=0x9: vfio 0000:07:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align Unraid 6.7.0-rc8 I have tried adding the alias line to my xml but that doesnt change anything, as the qemu code is also need. Is there anything i must do or should i be patient? EDIT: While i wait patiently i have rolled back to rc7 and all is well. Edited May 8, 2019 by raidserver Quote Link to comment
cybrnook Posted May 9, 2019 Share Posted May 9, 2019 (edited) 21 hours ago, raidserver said: Struggling to passthrough nvme drive too. Crucial CT1000P1SSD8 P1 1 TB [c0a9:2263] 07:00.0 Non-Volatile memory controller: Micron/Crucial Technology Device 2263 (rev 03) internal error: qemu unexpectedly closed the monitor: 2019-05-08T16:39:22.718254Z qemu-system-x86_64: -device vfio-pci,host=07:00.0,id=hostdev3,bus=pci.0,addr=0x9: vfio 0000:07:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align Unraid 6.7.0-rc8 I have tried adding the alias line to my xml but that doesnt change anything, as the qemu code is also need. Is there anything i must do or should i be patient? EDIT: While i wait patiently i have rolled back to rc7 and all is well. If you read the release notes of rc8, you will see a patch to work with SM controller NVME's was reverted in favor of another method: Quote Removed kernel patch which was trying to work around problematic Silicon Motion SM2262/SM2263 NVMe controllers. A different workaround is recommended. https://bugzilla.kernel.org/show_bug.cgi?id=202055#c42 I assume you didn't follow the new method? Edited May 9, 2019 by cybrnook Quote Link to comment
raidserver Posted May 9, 2019 Share Posted May 9, 2019 (edited) thanks cybernook, after a bit of fumbling around with the xml iam now at the stage of booting windows which is hanging on boot loading window. I no longer receive the error stated. heres my xml, maybe i have overlooked something. Reinstalled 6.7 rc8 EDIT: added vm log which shows an error near end. win8.1 xml.txt vm log.txt Edited May 9, 2019 by raidserver Quote Link to comment
raidserver Posted May 9, 2019 Share Posted May 9, 2019 With a good dose of patience windows has made it to desktop via VNC i see the NVME drive. Performance is terrible though it takes forever to boot & shutdown. the VM log is showing 2019-05-09T16:48:18.233068Z qemu-system-x86_64: warning: guest updated active QH spamming the log tail Quote Link to comment
limetech Posted May 9, 2019 Share Posted May 9, 2019 Something else to try: create the file /boot/config/vfio-bind with a line that specifies the PCI ID of your nvme device and then reboot for it to take effect. Take a look at /usr/local/sbin/vfio-pci script for more details. If you post diags I can tell you the exact string to use but you can prob figure it out. This might not make any difference but would be good to know that. Quote Link to comment
raidserver Posted May 9, 2019 Share Posted May 9, 2019 (edited) EDIT: Thanks but i have sent it back for a different drive. Will try again in the future. Edited May 10, 2019 by raidserver Quote Link to comment
zinkpro45 Posted May 11, 2019 Share Posted May 11, 2019 Final Release of 6.7 completely broke my windows VM with the 2262 controller. Used the workaround that was stated in the link above. Reverted back to RC5. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.