Solidigm

MLill · ‎02-21-2019

I'm trying to passthrough (kvm/qemu vfio-pci passthrough) an Intel 660P 2TB drive. This fails the sanity check with the following error:

Error starting domain: internal error: qemu unexpectedly closed the monitor: 2019-02-21 10:08:25.261+0000: Domain id=1 is tainted: host-cpu

2019-02-21T10:08:28.947450Z qemu-system-x86_64: -device vfio-pci,host=0a:00.0,id=hostdev5,bus=pci.7,addr=0x0: vfio error: 0000:0a:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align

Traceback (most recent call last):

File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in cb_wrapper

callback(asyncjob, *args, **kwargs)

File "/usr/share/virt-manager/virtManager/asyncjob.py", line 111, in tmpcb

callback(*args, **kwargs)

File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 66, in newfn

ret = fn(self, *args, **kwargs)

File "/usr/share/virt-manager/virtManager/domain.py", line 1420, in startup

self._backend.create()

File "/usr/lib64/python3.7/site-packages/libvirt.py", line 1080, in create

if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)

libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor: 2019-02-21 10:08:25.261+0000: Domain id=1 is tainted: host-cpu

2019-02-21T10:08:28.947450Z qemu-system-x86_64: -device vfio-pci,host=0a:00.0,id=hostdev5,bus=pci.7,addr=0x0: vfio error: 0000:0a:00.0: failed to add PCI capability 0x11[0x50]@0xb0: table & pba overlap, or they don't fit in BARs, or don't align

After reading about the issue here: https://patchwork.kernel.org/patch/10707761/

It seems to me that this could be fixed with a firmware update.

Is this something that is being looked at, at the moment?

Best regards.

Santiago_A_Inte · ‎04-24-2019

Hi MLill,

Greetings from Intel® SSD Support Group.

Please accept our apologies for our belated reply, we needed to investigate about your inquiry; today, we can share the following details with you:

We have reached our business unit (BU) and according to BU updates, we were not able to replicate the issue that you are seeing. It will be extremely helpful, if you can provide a log for the issue (lspci -vvv).

On the other hand, it seems that a workaround has been applied based on the information available here: https://bugzilla.kernel.org/show_bug.cgi?id=202055 you might want to take a look on this website.

Looking forward to hearing from you.

Have a nice day.

Santiago A.

Intel® Customer Support Technician

Under Contract to Intel Corporation

Third Party Content: Web Sites and Materials may contain user or third party submitted content; such content is not reviewed, approved or endorsed by Intel and is provided solely as a convenience to our customers and users. Under no circumstances will Intel be liable in any way for any third party submitted or provided content, including, but not limited to, any errors or omissions, or damages of any kind. ANY MATERIAL DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE MATERIALS IS DONE AT YOUR OWN DISCRETION AND RISK AND THAT YOU WILL BE SOLELY RESPONSIBLE FOR ANY DAMAGE TO YOUR COMPUTER SYSTEM OR OTHER DEVICE OR LOSS OF DATA THAT RESULTS FROM THE DOWNLOAD OF ANY SUCH MATERIAL. By your use you agree that you must evaluate, and bear all risks associated with, the use of any third party content, including any reliance on the accuracy, completeness, or usefulness of such content. All postings and use of the Web Sites or Material are subject to these Terms of Use and any other program and site specific terms.

View solution in original post

JosafathB_Intel · ‎04-26-2019

Hello MLill, Thank you for having contacted Intel® Memory & Storage Support. This is just a friendly reminder that your case remains open. Should you need our technical assistance please do not hesitate to contact us back. Best regards, Josh B. Intel® Customer Support Technician Under Contract to Intel Corporation

Santiago_A_Inte · ‎05-01-2019