Currently I have working passthrough with the hardware specs list below in the htread.

 

On a clean boot if I run "xl pci-assignable-list" it is blank.

There is a catch, I have to run x pci-assignable-add XXXXXXX every time unraid reboots.

You can see the series of commands I run to make it to work below.

 

In my syslinux.cfg I have added the hardware addresses to pciback.hide but it seems to have no affect.

 

If I boot my windows VM without running those commands no hardware gets passed through.

 

Does anyone have any thoughts on what I can do to make my pciback.hide list actually work?

 

My syslinux.cfg

root@Vault:/boot/syslinux# cat syslinux.cfg
default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  kernel /bzimage
  append initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
label Xen/unRAID OS
  menu default
  kernel /syslinux/mboot.c32
  append /xen xsave=1 cpufreq=xen:performance dom0_mem=1536M,max:2048M dom0_max_vcpus=1 dom0_vcpus_pin iommu=1 xen-pciback.hide=(05:00.0)(05:00.1)(00:10.0)(00:10.1) --- /bzimage console=tty0 --- /bzroot
label Xen/unRAID OS Safe Mode (no plugins)
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot unraidsafemode

 

My Windows 8 cfg file

 

name = 'Windows-8.1'
builder = 'hvm'
vcpus = '2'
memory = '2048'
device_model_version="qemu-xen-traditional"
disk = [
        'phy:/mnt/cache/VM/win8/win8.img,hda,w',
        #'file:/mnt/user/Apps/VMs/Win_Ent_8.1_64BIT.ISO,hdc:cdrom,r'
]
vif = [ 'mac=00:16:3E:ef:ef:ef,bridge=br0,model=e1000' ]
on_poweroff = 'destroy'
on_reboot = 'restart'

 

The commands I run before starting my Win8 VM

root@Vault:~# xl pci-assignable-list
root@Vault:~# xl pci-assignable-add 05:00.0
libxl: warning: libxl_pci.c:654:libxl__device_pci_assignable_add: 0000:05:00.0 not bound to a driver, will not be rebound.
root@Vault:~# xl pci-assignable-add 05:00.1
libxl: warning: libxl_pci.c:654:libxl__device_pci_assignable_add: 0000:05:00.1 not bound to a driver, will not be rebound.
root@Vault:~# lspci
00:00.0 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Root Complex
00:00.2 IOMMU: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) I/O Memory Management Unit
00:01.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Trinity [Radeon HD 7660D]
00:01.1 Audio device: AMD/ATI [Advanced Micro Devices, Inc.] Trinity HDMI Audio Controller
00:02.0 PCI bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Root Port
00:05.0 PCI bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Root Port
00:10.0 USB controller: AMD [Advanced Micro Devices, Inc.] FCH USB XHCI Controller (rev 03)
00:10.1 USB controller: AMD [Advanced Micro Devices, Inc.] FCH USB XHCI Controller (rev 03)
00:11.0 SATA controller: AMD [Advanced Micro Devices, Inc.] FCH SATA Controller [AHCI mode] (rev 40)
00:12.0 USB controller: AMD [Advanced Micro Devices, Inc.] FCH USB OHCI Controller (rev 11)
00:12.2 USB controller: AMD [Advanced Micro Devices, Inc.] FCH USB EHCI Controller (rev 11)
00:13.0 USB controller: AMD [Advanced Micro Devices, Inc.] FCH USB OHCI Controller (rev 11)
00:13.2 USB controller: AMD [Advanced Micro Devices, Inc.] FCH USB EHCI Controller (rev 11)
00:14.0 SMBus: AMD [Advanced Micro Devices, Inc.] FCH SMBus Controller (rev 14)
00:14.3 ISA bridge: AMD [Advanced Micro Devices, Inc.] FCH LPC Bridge (rev 11)
00:14.4 PCI bridge: AMD [Advanced Micro Devices, Inc.] FCH PCI Bridge (rev 40)
00:14.5 USB controller: AMD [Advanced Micro Devices, Inc.] FCH USB OHCI Controller (rev 11)
00:15.0 PCI bridge: AMD [Advanced Micro Devices, Inc.] Hudson PCI to PCI bridge (PCIE port 0)
00:18.0 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Function 0
00:18.1 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Function 1
00:18.2 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Function 2
00:18.3 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Function 3
00:18.4 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Function 4
00:18.5 Host bridge: AMD [Advanced Micro Devices, Inc.] Family 15h (Models 10h-1fh) Processor Function 5
01:00.0 RAID bus controller: Marvell Technology Group Ltd. MV64460/64461/64462 System Controller, Revision B (rev 01)
03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
05:00.0 VGA compatible controller: AMD/ATI [Advanced Micro Devices, Inc.] Cedar [Radeon HD 5000/6000/7350 Series]
05:00.1 Audio device: AMD/ATI [Advanced Micro Devices, Inc.] Cedar HDMI Audio [Radeon HD 5400/6300 Series]
root@Vault:~# xl pci-assignable-add 00:10.0
root@Vault:~# xl pci-assignable-add 00:10.1
root@Vault:~# xl pci-assignable-list
0000:00:10.0
0000:00:10.1
0000:05:00.0
0000:05:00.1
root@Vault:~#

 

My hardware setup

 

System "Name" - Vault

Xen capable? - Yes.

PCI Passthrough capable? - Yes.

 

• Case - Hiper Osiris
  
• CPU - AMD A10 5800k FM2
  
• Motherboard- MSI FM2-A85XA-G43
  
• GPU
  
  • Onboard - AMD Radeon HD 7660D
    
  • PCIe ATi 5450 Passthrough Win7
    

  [*]RAM 8gb ddr3

  [*]PSU - Corsair 550w

  [*]HBA / SAS Card - Supermicro AOC SASLP PCIe

  [*]NIC(s)

  • Onboard [disabled b/c I hate realktek] - Untested for unraid, but im sure it works, its a realtek 81xx chip.
    
  • Intel 1x PCIe NIC
    

  [*]Hard drives

  • 3TB x 3
    
  • 2TB x 2
    
  • 500gb x 1 cache
    

 

Brief description of VMs and use cases

 

Dom0 - unRAID

DomU1 - Ubuntu 12.04 no passthrough

DomU2 - Win8.1 w/passthrough of PCIe 5450 and onboard USB 3.0 controller from mobo

A quick glance tells me that your syslinux file looks OK but maybe its worth just double checking for typos etc.

 

Its that file which will tell unraid which stuff to pass to Xen (or another of putting it is excluded from unraid).

 

So my advice is double check what you have on the xen-pciback entry against other posts around the forums.

 

Sent from my Nexus 5 using Tapatalk

 

 

I would move the pciback.hide after the /bzimage and try again.

I would move the pciback.hide after the /bzimage and try again.

Thanks, I'll give this a shot next time I need to reboot unraid.

 

EDIT: Moving the xen-pciback.hide= after the /bzimage fixed the issue!