dev_codec

Members
 View Profile  See their activity

  • Posts

    3

  • Joined

  • Last visited

 Content Type 

Everything posted by dev_codec

  1. dev_codec
    I found out what is causing this, its something to do with the nvme drive itself. I was trying to pass-though a Mushkin Pilot (MKNSSDPL250GB-D8), uses a SMI SM2262 for its controller. However I just tried a samsung pm961 and it worked just fine. Very odd, this must be an issue with kvm or maybe the nvme is not made to spec. Edit: Ill also add that i had 2 of the pilots in my system, not sure if that would some how make a difference but thought i would add it. I would like to test it again with only one but I have no way to.
  2. dev_codec
    I am also getting this error and have been unable to get around it. Subbing the device made no difference for me. I even tried installing just ubuntu on the server and using kvm myself and ran in to this same issue again. Are some motherboards just not able to do this? Running a 8600k in a MSI Z370M Mortar motherboard. Edit: Was able to confirm my motherboard has VT-D and it is enabled.
  3. dev_codec
    I have an nvme drive i'm thing to pass though to a vm and so far i have made sure i am booting in uefi mode for unraid and added vfio-pci.ids=126f:2262 to my syslinux config so i stubbed them from my system. When i go to make a vm i can see the drive in the other pci devises section, but if i try and make a vm with it selected i get this. This is without me doing any xml editing. unraid-diagnostics-20180711-0005.zip