[SOLVED] HBA driver is loaded by Proxmox before it can be loaded by VM

[austin2118ace]

Hi All,

After installing Proxmox, I set up a TrueNAS VM with PCI passthrough of my HBA. Everything worked fine, I set up my ZPOOL and had my shares created. I rebooted the server to do some configuration changes, and now the HBA is loaded by Proxmox prior to the VM starting. The VM now fails to start since it no longer has access to the HBA. How do I prevent Proxmox from attaching the HBA so the VM can pick it up once it starts?

Thanks!

 

[Dunuin]

You could blacklist the HBA drivers like described in the wiki for GPU passthrough: https://pve.proxmox.com/wiki/Pci_passthrough

 

[austin2118ace]

You could blacklist the HBA drivers like described in the wiki for GPU passthrough: https://pve.proxmox.com/wiki/Pci_passthrough

That didn't seem to work. I used lspci -nn to get its device ID, which seems to be 03:00 1000:0087. In my /etc/modprobe.db folder there are two files, vfio.conf and pve-blacklist.conf. The contents of which are listed in the second screenshot. After editing both files I ran update-initramfs -u -k all and proxmox-boot-tool refresh
Any idea what I could have done wrong here?

 

[austin2118ace]

I ended up answering my own question.

In pve-blacklist.conf, each blacklist DRIVERNAME entry must be on separate lines. Moved it to a new line, updated and rebooted and works now!

 

[Neobin]

Regarding best practices it would be better to use a separate blacklist file like /etc/modprobe.d/blacklist.conf as described in the wiki, because you never know if the default pve-blacklist.conf might be overwritten in the future with an update.

 

[austin2118ace]

Regarding best practices it would be better to use a separate blacklist file like /etc/modprobe.d/blacklist.conf as described in the wiki, because you never know if the default pve-blacklist.conf might be overwritten in the future with an update.

Thanks for the info, could you link to that section of the wiki, I must have missed it when I read it earlier.